ACS Commons Dispatcher Flush Agent breaks Replication:Error while replicating content com.day.cq.replication.AccessDeniedException | Community
Skip to main content
dewanshis189253
January 21, 2019

ACS Commons Dispatcher Flush Agent breaks Replication:Error while replicating content com.day.cq.replication.AccessDeniedException

  • January 21, 2019
  • 1 reply
  • 3331 views

Hi Team,

I am using AEM Version: 6.4 and ACS Commons : 3.18.2 and have written Dispatcher Flush Rules using ACS Commons Configuration. I am getting below error and Replication breaks while replicating pages

Dispatcher Flush Rules :

  • /etc/packages/(.+)/.*=/etc.clientlibs/$1&/etc.clientlibs/common  
  • /apps/(.+)/clientlibs/.*=/etc.clientlibs/$1

Please help me on this.

Thanks

Dewanshi

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

1 reply

Gaurav-Behl
January 21, 2019

If you use ACS flush agent, then you would need to configure appropriate ACLs for 'acs-commons-dispatcher-flush-service' user mentioned in docs.

Check if 'acs-commons-dispatcher-flush-service' user has read access on the content path that you are trying to flush.

On a side note, the flush rules doesn't seem to be appropriate to me. Please validate/fix, if required. 

dewanshis189253
January 21, 2019

Hi Gaurav,

Thanks for your response . I have checked that user acs-commons-dispatcher has read access. Please find below screenshot.

Above mentioned dispatcher rules working fine in DEV ,So I don't think that dispatcher flush rules are inappropriate.

Thanks

Dewanshi

Gaurav-Behl
January 21, 2019

Could you check the same permissions are applied to /content or /content<root>/au/en node where you see the error?

For first flush rule -

  • /etc/packages/(.+)/.*=/etc.clientlibs/$1&/etc.clientlibs/common  -- means the <group-name> and <package-name> under /etc/packages would be picked up for flushing. E.g.  /etc/packages/my_package/abc.zip  would be applied as /etc.clienlibs/my_package/abc.zip......

I'm not able to think of any reason to flush package name. The other path of /apps/<project-root>/ makes sense to me.

Since you are trying to flush /etc/packages and /apps/<project-root> paths, could you also validate if acs-commons-dispatcher-flush-service has access to /etc/packages and /apps/<project-root> per your use case?