Wednesday, September 11

Replication queue is blocked on Adobe/Day CQ5

Impact: Authors are able to create and
activate content, but the activated pages are not updated on the CQ5 publish
instances. (Forward replication has issues) This means end users may see stale
content.End users are able to update user related data however they are not being replicated to Author instances,
or different publisher instances have gone out of sync on data. (Reverse
replication has issues)

Overview

Adobe CQ facilitates the concept of managing content on
publisher instance by creating/ modifying the content of author site and then
replicating the same content on all publisher instances. It does not require
server restart so replication in CQ is seamless and just in time. For
replication process to work smoothly, It is must that replication
infrastructure like queues and agents are functioning properly. Replication
agents are configured and managed via Admin Console CQ

Issue

Any content being activated from
author site is not being replicated on publisher instances (in case of forward
replication queues are blocked). Similarly any content changes on publisher are
not being reverse replicated to Author (in case of reverse replication queues
are blocked). So website users won’t be able to view updated content. Data
among multiple instances can become out of sync depending on the instances
between which queues are blocked.

Resolution

The resolution is to make sure that the replication agents
are fine and the blocked messages on queues are cleaned up.

• Go to the list of replication agents
(/etc/replication/agents.author.html). Access replication agent console to view the list of agents.
• for each replication agent, do the following:

1.Make
sure that the agent is enabled. For every replication agent status should
display ‘enabled’

2.Verify
the connectivity with the publish instance by clicking on the "Test
Connection" link; if it fails, make sure that on TCP network level, the
server hosting the CQ author instance can connect to the port of thepublish instance

4.Make
a note of first payload path in replication queue. Then try to clear the 1st
element of the replication queue, and verify if the replication resumes. Once
it resumes activate the first payload noted above in the queue again. Payload
can be activated by right clicking on content on author site and selecting
activate option.

5.Check
with the CRX
Content Explorer that there is no /bin/receive node on the publish instance,
otherwise delete it. This will ensure the failed replication clean up and
content received on publisher will not be duplicated.

6.Check
with the CRX
Content Explorer that there is no /bin/replicate node on the author
instance, otherwise delete it. This will ensure the failed replication clean up
and content available on author for replication will not be duplicated.

7.In
case the logs show no replication attempt since a few minutes, restart the
replication bundle in the Felix
console; if there's still no replication attempt in the replication logs
then restart the Apache
Sling Event Support bundle

Verification

8.

1.The
content that has been activated above in Step 4 should be verified at Publisher as well as dispatcher.

Subscribe via email

About Me

Mobile NO : 7503454801
Email address : manojbharal2@gmail.com
About Blog
Blog consist of posts on java j2ee technical topics. It covers all range of post starting with basic java questions up to advanced j2ee architecture. I am owning this blog. Content being published here is authentic and original . This is growing blog and visitors can expect huge relevant and useful information to enhance their knowledge on subject.
About me
I have total of around 8 years of experience in java j2ee technologies and am working on multiple business domain technical projects in all range of industries .