search

Adobe-Consulting-Services / acs-aem-commons

http://adobe-consulting-services.github.io/acs-aem-commons/
Apache License 2.0
453 stars 597 forks source link

ACS Common - Dispatcher Flush Not working #3384

Open manishkgithub opened 1 month ago

manishkgithub commented 1 month ago

Required Information

Dispatcher cache should get cleared, but its not working in Production environment. In lower Environment (like stage) it is working fine. It should clear the mentioned path cache.

When trying to clear dispatcher cache, we are getting error. We have 2 dispatchers which has been setup correctly in dispatcher flush configuration. When selecting invalidate cache and providing the required path which needs to be cleared, we are getting error message "An error occurred during replication. Possible issues include invalid flush path or lack or active dispatcher flush agents. Please review your Dispatcher Flush agent logs to ensure all replication requests were successfully processed."

In replication agent (author) getting below error message: Error while sending request: Java.net.ConnectException: Connection timed out (Connection timed out)

Its working fine lower environment like in stage, it is working fine and cache is getting cleared.

Checked dispatcher IPs configured in dispatcher flush and they are correct.

Steps to Reproduce

Starting from a vanilla instance of AEM at the above version, describe in explicit steps how to reproduce. Link to any supporting assets, e.g. content packages, below

image

Error_Details.docx

manishkgithub commented 1 month ago

Can anyone suggest what could be the issue here and how to get this ACS Common Dispatcher flush work in this case. Thanks in advance

davidjgonzalez commented 1 month ago

I assume youre triggering this from AEM Author? Can you test the flush against the AEM flush agents youre targeting, and make sure they can test OK using the AEM's replication agent UI?

Based on the error, it seems like either

  1. Your flush agents aren't pointing to the right host/IPs
  2. Something is blocking this traffic between this AEM and the Dispatcher

You do have to configure Dispatcher to allow flushing from specific IPs, but i dont think you get this error (maybe tho - its been a while).