Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

AEM content package replication - performance issue

Balu_M
Level 3
Level 3

Hi All,

 

We are replicating content package(content.zip) from one instance to another instance using automated process but we are getitng issue with replication process, sometimes replication of package(~20 mb) taking 1hr to replicate. we captured processing time of replication job from "/system/console/slingevent" console.

 

Any suggestions to debug this issue ?

 

Thanks,

Balu.

 

 

1 Accepted Solution
Raja-kp
Correct answer by
Level 7
Level 7

@Balu_M Content package of 20mb won't be taking 1hr to replicate the package to publisher.

  1. Can you check the replication log during the replication process.
  2. Check error.log as well.
  3. Try to activate the content package manually to verify the time duration whether automated process causing the issue.
  4. Check OSGi configuration : Package Manager validation configuration -> to check package size & time limit validation.

Let us know how you are trying to replicate the content package to another instance via automated process?

View solution in original post

2 Replies
Raja-kp
Correct answer by
Level 7
Level 7

@Balu_M Content package of 20mb won't be taking 1hr to replicate the package to publisher.

  1. Can you check the replication log during the replication process.
  2. Check error.log as well.
  3. Try to activate the content package manually to verify the time duration whether automated process causing the issue.
  4. Check OSGi configuration : Package Manager validation configuration -> to check package size & time limit validation.

Let us know how you are trying to replicate the content package to another instance via automated process?

Jörg_Hoh
Employee
Employee

As mentioned, you should check the error.log; when the replication has been completed, it will print a longer log line with multiple durations; from there it should be visible in which part of the replication process the time is spent.