even though replication agent is deleted, job queues still fill up | Community
Skip to main content
JS_Bournival
JS_Bournival
Level 3
October 16, 2015
Solved

even though replication agent is deleted, job queues still fill up

  • October 16, 2015
  • 4 replies
  • 3945 views

We have this strange problem.  We had a flush cache replication agent on the author. It was disabled. But the associated job queue still accumulate a lot of job, these job obviously failed, and they seem to retry again and again.

Here's a log entry:

10.04.2015 00:00:29.640 *ERROR* [pool-6-thread-18-com/day/cq/replication/job/flush_dispn1(com/day/cq/replication/job/flush_dispn1)] com.day.cq.replication.impl.AgentManagerImpl Job contains agent which is not started: flush_dispn1. waiting ReplicationJob{event=org.osgi.service.event.Event [topic=com/day/cq/replication/job/flush_dispn1]}

Now, since it's unused, we tried deleting the replication agent, but the queue stays there, and jobs still append to it.  What can we do to get rid of this?

Thanks.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Sham_HC

Deleting agent does not clear the jobs.  Do not know your aem version to specify the exact path . Clear the job from /var/eventing/jobs or the query to find location is [1]. Clearing it should resolve your issue.

[1]   /jcr:root/var/eventing//*[@event.job.topic = 'com/day/cq/replication/job/flush_dispn1']

4 replies

smacdonald2008
smacdonald2008
Level 10
October 16, 2015

Take a look at this knowledge base article and trouleshooting infomation- see if they help:

https://helpx.adobe.com/experience-manager/kb/replication-stuck.html

http://docs.adobe.com/docs/en/aem/6-0/deploy/troubleshoot-rep.html

If this is an issue not in these topics - let us know. 

Sham_HC
Sham_HCAccepted solution
Level 10
October 16, 2015

Deleting agent does not clear the jobs.  Do not know your aem version to specify the exact path . Clear the job from /var/eventing/jobs or the query to find location is [1]. Clearing it should resolve your issue.

[1]   /jcr:root/var/eventing//*[@event.job.topic = 'com/day/cq/replication/job/flush_dispn1']

    JS_Bournival
    JS_BournivalAuthor
    Level 3
    October 16, 2015

    Thanks for the quick answer Scott.

    Actually, since the replication agent is gone, how can I delete the queue? I looked for it in the job queue configurations, I cannot find it.

    We first thought that by disabling the replication agent it might also disable the job queues, but no. We still got the logs of its attempts.

    smacdonald2008
    smacdonald2008
    Level 10
    October 16, 2015

    This may be a bug - I will have Sham look at this to see if it's known issue. 

    Terms & ConditionsAccessibility statement

    Loading footer...