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

Issue with replication agents

kishore_geddamu
Level 2
Level 2

Hi All,

We have 12 replication agents for our application and out of 12 ,6 are working fine .For remaining replication agents i am seeing below error.

30.05.2014 02:01:11.771 *ERROR* [pool-25-thread-24-com_day_cq_replication_job_default-agent-wjb2stl51-14(com/day/cq/replication/job/default-agent-wjb2stl51-14)] com.day.cq.replication.impl.ReplicationContentFactoryProviderImpl Unable to update 'agents' property of /var/replication/data/8bdd0319-3349-4815-af30-797ba5a9ae09/0a/0a087982-d6f0-48e5-bf2e-9d663c6a3f21 after 10 attempts

30.05.2014 04:00:08.314 *ERROR* [pool-25-thread-25-com_day_cq_replication_job_default-agent-wjb2stl51-12(com/day/cq/replication/job/default-agent-wjb2stl51-12)] com.day.cq.replication.impl.ReplicationContentFactoryProviderImpl Unable to update 'agents' property of /var/replication/data/8bdd0319-3349-4815-af30-797ba5a9ae09/87/875c1bc0-b344-438e-b2e6-00f3959d68c7 after 10 attempts

30.05.2014 04:00:52.271 *ERROR* [pool-25-thread-23-com_day_cq_replication_job_default-agent-wjb2stl51-12(com/day/cq/replication/job/default-agent-wjb2stl51-12)] com.day.cq.replication.impl.ReplicationContentFactoryProviderImpl Unable to update 'agents' property of /var/replication/data/8bdd0319-3349-4815-af30-797ba5a9ae09/c5/c5d4aefe-26e7-4811-9733-7b761fe3f6cc after 10 attempts

30.05.2014 04:00:55.786 *ERROR* [pool-25-thread-10-com_day_cq_replication_job_default-agent-wjb2stl51-11(com/day/cq/replication/job/default-agent-wjb2stl51-11)] com.day.cq.replication.impl.ReplicationContentFactoryProviderImpl Unable to update 'agents' property of /var/replication/data/8bdd0319-3349-4815-af30-797ba5a9ae09/7c/7c0fe4db-2285-4d28-abfc-d9a2ae0a5934 after 10 attempts

If anyone has encountered this king error.Please help me.

Thanks,

KG

1 Accepted Solution
Sham_HC
Correct answer by
Level 10
Level 10

Kishore Geddamu wrote...

Sham HC wrote...

Exceptions indicate that multiple crx sessions trying to save a node concurrently.  1 session wins and other session logs this exception. It's expected behavior.  Are you seeing queue getting stuck?    Any possibility for you to try with enabling file system based durbo ?

 

Thanks Sham.

Our replication queue is not getting stuck.And more over we don't have access to chekc out file system.

 

IMO as informed earlier it is lower level log should not printed at error log level & prints during concurrency update.  can ignore  in case the queue get stuck please file daycare. 

View solution in original post

3 Replies
Sham_HC
Level 10
Level 10

Exceptions indicate that multiple crx sessions trying to save a node concurrently.  1 session wins and other session logs this exception. It's expected behavior.  Are you seeing queue getting stuck?    Any possibility for you to try with enabling file system based durbo ?

kishore_geddamu
Level 2
Level 2

Sham HC wrote...

Exceptions indicate that multiple crx sessions trying to save a node concurrently.  1 session wins and other session logs this exception. It's expected behavior.  Are you seeing queue getting stuck?    Any possibility for you to try with enabling file system based durbo ?

 

Thanks Sham.

Our replication queue is not getting stuck.And more over we don't have access to chekc out file system.

Sham_HC
Correct answer by
Level 10
Level 10

Kishore Geddamu wrote...

Sham HC wrote...

Exceptions indicate that multiple crx sessions trying to save a node concurrently.  1 session wins and other session logs this exception. It's expected behavior.  Are you seeing queue getting stuck?    Any possibility for you to try with enabling file system based durbo ?

 

Thanks Sham.

Our replication queue is not getting stuck.And more over we don't have access to chekc out file system.

 

IMO as informed earlier it is lower level log should not printed at error log level & prints during concurrency update.  can ignore  in case the queue get stuck please file daycare. 

View solution in original post