AEM 6.3: Author -> dispatcher flush also executes replication event to publishers

Avatar

Avatar

Jdruwe

Avatar

Jdruwe

Jdruwe

16-01-2019

Let me first describe our 2 agents on our author environment:

- Dispatcher flush agent (we have a dispatcher in front of our author environment to add an extra layer of caching for the content authors)

- Default agent (used for publishing to the publish environment)

NOTE: obviously 2 different entities.

The dispatcher flush agent is new in our setup and gets trigger on modification. After adding the agent our content author complained that their changes were automatically published for some reason. After some investigation/debugging of the com.day.cq.replication.impl.ReplicatorImpl it seems that there is also a replication event fired by the RolloutManager with the following ReplicationOptions (note: no AgentIdFilter or ReplicateOnModification filter)

ReplicationOptions{synchronous=false, revision='null', suppressStatusUpdate=false, suppressVersions=false, filter=null, aggregateHandler=null}

No filter results in all enabled agents to be triggered so the path will get replicated to the publishers, NOT wat we want...

1669544_pastedImage_0.png

It seems to me the the combination of a dispatcher flush agent and default agent is not working properly. Anyone experiencing the same problems?

Replies

Avatar

Avatar

Jörg_Hoh

Employee

Total Posts

3.0K

Likes

953

Correct Reply

1.0K

Avatar

Jörg_Hoh

Employee

Total Posts

3.0K

Likes

953

Correct Reply

1.0K
Jörg_Hoh
Employee

30-01-2019

Your dump indicates to me, that the MSM rollout invokes the TargetActivateActionFactory, which invokes replication. And this replication might trigger all agents. But that seems no match to your initial problem description, because there I read it in this way: The invalidation agent (with on-modification trigger set) causes the "standard" replication to get fired.

Avatar

Avatar

Jdruwe

Avatar

Jdruwe

Jdruwe

30-01-2019

Yes, when I enable it, it does trigger the other default replication for some reason. So it still seems like a bug to me.