Expand my Community achievements bar.

Enhance your AEM Assets & Boost Your Development: [AEM Gems | June 19, 2024] Improving the Developer Experience with New APIs and Events
SOLVED

Publication pending AEM 6.5

Avatar

Level 7

I used Tree Activation to publish a big directory structure and now I have a around 27000 object in the queue. It is taking a very long time. Where can I see the publication queue to verify it is indeed processing the pages?

 

I checked the publication agent https://author-instance/etc/replication/agents.author/publish.html 

Agent that replicates to the default publish instance.

How come the queue is not active and the status of my sites on the author instance report that they are in the queue for publishing. I have one author instance and two publish instances.

anasustic_0-1713623221132.pnganasustic_1-1713623304745.png

 

1 Accepted Solution

Avatar

Correct answer by
Level 4

Hi @anasustic ,

 

If your AEM is managed by AMS then , adobe team will create a new replication agent with ALB url but not with actual publish URL. If you are unable to find the replication agent which is configured with ALB url then get the ALB url and just replace host and port in the transport URI ad test connection and trigger replication again. 

 

Since you already triggered replication right, you can find the default replication agent in var/eventing crx path and you can delete the date nodes or go to /system/console/slingevent and find which replication agent is scheduled and waiting. 

 

After deleting the alredy scheduled replication items in the sling job, find or configure the  the replication agent with ALB url and you can trigger the replication again.

 

 

 

View solution in original post

2 Replies

Avatar

Community Advisor

@anasustic I don't think this is topic for EDS.. @Jagpreet_Singh_ can you move this to aem bucket??

 

To answer your question to can you goto to replication agents on author page and see if any other agents are in active state? In most cases, AMS will create different agents to configure replication agents instead of using ootb publish agent.

 

https://author-instance/etc/replication/agents.author.html

Avatar

Correct answer by
Level 4

Hi @anasustic ,

 

If your AEM is managed by AMS then , adobe team will create a new replication agent with ALB url but not with actual publish URL. If you are unable to find the replication agent which is configured with ALB url then get the ALB url and just replace host and port in the transport URI ad test connection and trigger replication again. 

 

Since you already triggered replication right, you can find the default replication agent in var/eventing crx path and you can delete the date nodes or go to /system/console/slingevent and find which replication agent is scheduled and waiting. 

 

After deleting the alredy scheduled replication items in the sling job, find or configure the  the replication agent with ALB url and you can trigger the replication again.