AEM Custom Replication Agent on Publish - queue not found

Avatar

Avatar
Validate 1
Level 2
srinir44531418
Level 2

Likes

2 likes

Total Posts

8 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Ignite 1
Give Back 5
Give Back 3
Give Back
View profile

Avatar
Validate 1
Level 2
srinir44531418
Level 2

Likes

2 likes

Total Posts

8 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Ignite 1
Give Back 5
Give Back 3
Give Back
View profile
srinir44531418
Level 2

10-10-2018

We have need to flush akamai cache on replication and built a custom agent following an (older) project on Github. GitHub - nateyolles/aem-akamai-replication-agent: How to create custom replication agents in AEM usi...

Then we created agent under "Agents on author". UI shows up, we can set configuration etc and agent makes calls to Akmai, all good.

However, same configuration when created on Publish instance, under "Agents on publish", does not work.  UI shows up, we can set configuration etc. However, there is debug message about "com.day.cq.replication.agent.akamai.queue Queue name com/day/cq/replication/job/akamai not found.  And on replicating content from author to publish, no calls are made into Transport Handler.

I checked the Felix Jobs console and typically the queue "com/day/cq/replication/job/akamai" would be created on author instance (when akamai agent is configure) as soon as first replication action is taken. However, no such queue topic is created on Publish no matter how we configure the agent on Publish.

Wondering if anyone know details around what code piece and when would it create queue topics for agents and is there is something else preventing the queue topic being created on publish ?    OOTB flush agent configured on Publish has corresponding queue topic created.

Appreciate it.

Replies

Avatar

Avatar
Springboard
MVP
Shashi_Mulugu
MVP

Likes

234 likes

Total Posts

295 posts

Correct reply

67 solutions
Top badges earned
Springboard
Bedrock
Validate 1
Applaud 100
Establish
View profile

Avatar
Springboard
MVP
Shashi_Mulugu
MVP

Likes

234 likes

Total Posts

295 posts

Correct reply

67 solutions
Top badges earned
Springboard
Bedrock
Validate 1
Applaud 100
Establish
View profile
Shashi_Mulugu
MVP

10-10-2018

Please refer to below links

queue for replication agent not found

  • Check whether the bundle is installed correctly.
  • Verify both content Builder and Transport Handler components are active.
  • Verify whether agent is enabled in configurations.
  • Post the test connection log

Avatar

Avatar
Validate 1
Level 2
srinir44531418
Level 2

Likes

2 likes

Total Posts

8 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Ignite 1
Give Back 5
Give Back 3
Give Back
View profile

Avatar
Validate 1
Level 2
srinir44531418
Level 2

Likes

2 likes

Total Posts

8 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Ignite 1
Give Back 5
Give Back 3
Give Back
View profile
srinir44531418
Level 2

10-10-2018

Thanks. I did review the other thread. That issue was result of space in the agent name (and on Author instance).

In our case, I can confirm that there are no spaces in the agent name (akamai).

Following scenario with works . on Author instance:

1. New agent created with name "akamai"

2. Content published

3. QueueTopic gets created (from OSGI Jobs screen)

4. Custom Transport Handler for the custom agent gets called

Following scenario does not work on Publish instance:

1. New agent created with name "akamai"

2. Content published from Author to Publish

3. QueueTopic is not created (from OSGi Jobs screen)

4. Custom Transport Handler is NOT invoked.

Only "message" we can find on Publish is the following. No exceptions or other errors.

----------

com.day.cq.replication.Agent.akamai.queue Queue com/day/cq/replication/job/akamai not found.

---------

Avatar

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,410 likes

Total Posts

12,671 posts

Correct reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,410 likes

Total Posts

12,671 posts

Correct reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile
smacdonald2008
Level 10

10-10-2018

This was for 6.1 - what version are you using?

Avatar

Avatar
Validate 1
Level 2
srinir44531418
Level 2

Likes

2 likes

Total Posts

8 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Ignite 1
Give Back 5
Give Back 3
Give Back
View profile

Avatar
Validate 1
Level 2
srinir44531418
Level 2

Likes

2 likes

Total Posts

8 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Ignite 1
Give Back 5
Give Back 3
Give Back
View profile
srinir44531418
Level 2

11-10-2018

We are using AEM 6.4 .  Are there changes in replication agent component / api that results in this behavior only on Publish ? Thanks.

Avatar

Avatar
Validate 1
Level 2
srinir44531418
Level 2

Likes

2 likes

Total Posts

8 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Ignite 1
Give Back 5
Give Back 3
Give Back
View profile

Avatar
Validate 1
Level 2
srinir44531418
Level 2

Likes

2 likes

Total Posts

8 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Ignite 1
Give Back 5
Give Back 3
Give Back
View profile
srinir44531418
Level 2

11-10-2018

Figured it out. The solution was quite obvious (and silly). Agents (specially the ones used for flushing activity) on publish need  "On Receive" checked on the Trigger tab of the agent configuration. And it also needs "Ignore Default" checked.  Looking back, it makes complete sense.