ACS commons Dispatcher Flush Delete Action not working | Community
Skip to main content
S
sanjays16398239
Level 2
July 11, 2017
Solved

ACS commons Dispatcher Flush Delete Action not working

  • July 11, 2017
  • 14 replies
  • 6770 views

Hi,

I have a page created with dispatcher flush template and an agent configured to clear the cache on my publish server. The flush action is set to Invalidate and it replicates successfully as per the logs but the replication paths or flush paths are not invalidated or touched. I tried setting the action to delete, but that errors out as below.

An error occurred during replication. Possible issues include invalid flush paths or lack of active dispatcher flush agents. Please review your Dispatcher Flush Agent logs to ensure all replication requests were successfully processed.

http://host:port/dispatcher/invalidate.cache is the URL I'm using for invalidating. Is there a different URL for delete Cache?

ACS Commons -3.5.2

Thanks

Sanjay

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

    Check out .. https://docs.adobe.com/docs/en/dispatcher/disp-config.html#Automatically Invalidating Cached Files  -- This should solve your problem. With your deny all, you're effectively doing resource-only flushing for everything.

    14 replies

    Show previous replies
    D
    Adobe Employee
    davidjgonzalezzzzAdobe EmployeeAccepted solution
    Adobe Employee
    July 17, 2017

    Check out .. https://docs.adobe.com/docs/en/dispatcher/disp-config.html#Automatically Invalidating Cached Files  -- This should solve your problem. With your deny all, you're effectively doing resource-only flushing for everything.

    S
    sanjays16398239Author
    Level 2
    July 17, 2017

    Thank you that resolved it, after adding allow for *.html

    S
    sanjays16398239Author
    Level 2
    July 17, 2017

    That worked for dispatcher flush agent but using { /glob "*.html" /type "allow" } caused the entire cache to be invalidated after activating a page in the directory

    joerghoh
    Adobe Employee
    joerghohAdobe Employee
    Adobe Employee
    July 17, 2017

    In that case you need to set the parameter "statfilelevel" correctly.

    Jörg

      Terms & ConditionsAccessibility statement

      Loading footer...