ACS Common Dispatcher Flush agent not working

[Maximilian_Voss]

Hi,

We are using ACS common (4.0.0) Dispatcher Flush page to flush dispatcher cache as scheduled job using Jenkins.

Our site have English and French content pages. Looks like French cached pages are not getting deleted...

Anyone seen these kind of issue before..?

[Maximilian_Voss]

Are the English & French website running on the same Apache vhost?

[Maximilian_Voss]

Are the English & French website running on the same Apache vhost?

What's the stat level on Dispatcher.any?

[Maximilian_Voss]

Are the English & French website running on the same Apache vhost?

[Mayukh007]

They are running from different vhosts. Stat level is 5 in english farm file and 3 in french farm file.

[Maximilian_Voss]

to which vhost is the invalidation call sent?

[Mayukh007]

each farm file have their own vhost, so french ones goes to french vhost and same for english farm.

[Maximilian_Voss]

do you see the calls coming in, in the log? What does the dispatchers debug log say?

[Mayukh007]

HI Maximilian_Voss, looks like the issue with French pages are that I was adding them with English page name but for some reason looks like the cache getting cleared if I add the pages in Dispatcher Flush page with French Title. The pages are getting stored in Dispatcher cache with French Title...Not sure what changed but it was always working with page name and there we were using same page name for both En and Fr....!!

[#10 · Accepted solution]

* Try running dispatcher flush manually from the instance on which the flush is configured.

You can try running a curl command. The following docs may be helpful:

https://experienceleague.adobe.com/docs/experience-manager-64/administering/operations/curl.html?lan...

https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/page-invalid...

If it doesn't work, it means it's something to do with access/permissions.

* If it works manually, but via ACS Commons it doesn't, try using one of the latest versions of ACS Commons. The issue might have been fixed in those.

I have seen many customers using 4.3.4 and above.

You can also log ACS Commons related issues here:
https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues