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

Replication queue is not active

harryjat
Level 2
Level 2

Hi All,

We have recently installed AEM 6.5 author and publish on JEE.

 

The publish server default agent queue is not active. 

Default Agent (publish)  : Queue is not active

I tried below link but id didnot worked for us. Could you please let us know what can be done.

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

 

ReplicationIssue.jpg

@mgandhi @mgandhi67 @MayankGandhi 

1 Accepted Solution
BrianKasingli
Correct answer by
Community Advisor
Community Advisor

@harryjat,

From the screenshot you've provided, it seems like your replication agent is disabled. I can see this because of the "red" icon. Typically when a specific replication agent is enabled, the icon should become "green".

Okay, next step. Assuming that you've re-configured the replication agent, and it still not show up as enabled. You need to check these things (please restart your AEM instance before proceeding to optimise your best testing environment):

  1. Error.log, tail the error.log in .../crx-quickstart/logs/error.log. What kind of errors do you see while trying to enable the specific replication agent?
  2. Run Modes; are you configuring the correct replication agent within the current context of the environment? To simplify things, use /etc/replication/agents.author/* on "author" run mode and /etc/replication/agents.publish/* on "publish" run mode. Let's not complicate things by adding custom run modes.

Once your agent is running, you should be able to see logs from the replicating agent coming in. Even if your dispatcher environment is not set up, when your replication agent is trying to perform a task, and if it fails of successes, logs should be shown in the "view logs" button within the configuration page of the replication agent. 

 

If you really want to test this mechanism from out of the box, green-field environment, in your local desktop, perform tasks below (by default, the replication configuration on the author instance will publish to localhost:4503):

  1. Startup a new AEM "author" instance, you can simply double click on the quickstart JAR (let's keep it with default settings, with samples,localhost:4502).
  2. At the same time, start up a new AEM "publish" instance, you can simply double click on the quickstart JAR (let's keep it with default settings, with samples, localhost:4503).
  3. Once both your local AEM author and AEM publish instances are running, you can simply replicate anything, and you should see a successful replication. (because by default, the replication to localhost:4503 publish agent is enabled on the author)

I hope this helps.

View solution in original post

5 Replies
sunjot16
Employee
Employee

Try clearing all browser cache & cookies, check Disable Cache checkbox in Network tab of Developer Tool, close all browser windows and open a new one in Incognito Window. Probably, try another browser, such as Mozilla Firefox in Incognito Mode to verify it again.

 

Also, try to recompile JSPs & rebuild clientlibs, if it still doesn't work.

https://helpx.adobe.com/experience-manager/kb/How-to-force-a-recompilation-of-all-Sling-scripts-jsps...

BrianKasingli
Correct answer by
Community Advisor
Community Advisor

@harryjat,

From the screenshot you've provided, it seems like your replication agent is disabled. I can see this because of the "red" icon. Typically when a specific replication agent is enabled, the icon should become "green".

Okay, next step. Assuming that you've re-configured the replication agent, and it still not show up as enabled. You need to check these things (please restart your AEM instance before proceeding to optimise your best testing environment):

  1. Error.log, tail the error.log in .../crx-quickstart/logs/error.log. What kind of errors do you see while trying to enable the specific replication agent?
  2. Run Modes; are you configuring the correct replication agent within the current context of the environment? To simplify things, use /etc/replication/agents.author/* on "author" run mode and /etc/replication/agents.publish/* on "publish" run mode. Let's not complicate things by adding custom run modes.

Once your agent is running, you should be able to see logs from the replicating agent coming in. Even if your dispatcher environment is not set up, when your replication agent is trying to perform a task, and if it fails of successes, logs should be shown in the "view logs" button within the configuration page of the replication agent. 

 

If you really want to test this mechanism from out of the box, green-field environment, in your local desktop, perform tasks below (by default, the replication configuration on the author instance will publish to localhost:4503):

  1. Startup a new AEM "author" instance, you can simply double click on the quickstart JAR (let's keep it with default settings, with samples,localhost:4502).
  2. At the same time, start up a new AEM "publish" instance, you can simply double click on the quickstart JAR (let's keep it with default settings, with samples, localhost:4503).
  3. Once both your local AEM author and AEM publish instances are running, you can simply replicate anything, and you should see a successful replication. (because by default, the replication to localhost:4503 publish agent is enabled on the author)

I hope this helps.

View solution in original post

harryjat
Level 2
Level 2

Hi @BrianKasingli

 

Thanks for your help. It will ceratinly help me in bossting my knowledge had i face replication issue in future.

 

I have "checked" some of the triggers i thought would be useful in our case. This has caused the issues.

When i "unchecked" all the triggers and used the out-of-box solution provided. Replication started working.

Thanks

harryjat
Level 2
Level 2
Hi @BrianKasingli Thanks for your help. It will ceratinly help me in bossting my knowledge had i face replication issue in future. I have checked some of the triggers i thought would be useful in our case. This has caused the issues. When i unchecked all the triggers and used the out-of-box solution provided. Replication started working. Thanks