AEM 6.5.2 - issue with cache invalidation of an alias | Community
Skip to main content
New Participant
December 6, 2019
Solved

AEM 6.5.2 - issue with cache invalidation of an alias

  • December 6, 2019
  • 4 replies
  • 1930 views

Hello,

Recently since upgrading to 6.5, i've been having issues with cache invalidation not happening on aliased locations during deactivation events.

eg. -  I have /content/test/en_US/testpage.html that would have an alias to /content/test/en/testpage.html

On activation of this page, I see the flush agent behaving properly for both the aliased and non aliased location.

However, if I then go to deactivate this page -

The page is deactivated and invalidated on the non aliased location, but remains in cache at the aliased location.

I do have the alias update checkbox selected on my flush agent on the publisher.

Any ideas what might cause this?

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

4 replies

santhosh_kumark
santhosh_kumarkAccepted solution
New Participant
December 8, 2019
Employee
December 7, 2019

I would recommend setting up a DEBUG logger on com.day.cq.replication to verify if the alias deactivation is getting triggered and then change the dispatcher log level to DEBUG to verify what's happening on dispatcher when this kind of request is requested.

New Participant
December 7, 2019

It was, we were using 6.2

joerghoh
Employee
December 7, 2019

Was this working before? What version were you using then?