Dispatcher Caching Issues

It depends in the stat file level. Dispatcher does not automatically invalidates the child pages even the replicated/parent page has iparsys.

Hi,

in that case it seems that the invalidation seems not to work correctly.

1. Can you validate that the dispatcher is setup properly?
2. Also check that the browser caching is not interfering
3. Can you do the tests without going through dispatcher?

Jörg

Hi

I'm Facing an issue

issue with iparsys caching on ‘Canceling inheritance’

I believe we might be able to reproduce the steps with Geometrixx site as that come up with an iparys.

Following steps are from our QA team for our custom implementation:

1. Create a DC footer with language, like dc/us/en
2. Re-edit the Inheritance of footer component in dc/us/en, checked “Cancel Inheritance”
3. Check the footer in prior page again – the footer is still show after refresh.
4. Checked on another page, which was not viewed in step#2(no cache), the page was loaded without footer.

If you like, you can raise a Daycare issue and ask for the improvement of the documentation. Especially if you get specific what in detail is confusing it's likely that the documentation will get updated.

(If you post the Daycare ticket ID, I can have a look at it :-))

Jörg

Thanks. It worked. The dispatcher documentation is little confused. I found below article is helpful.

http://aempodcast.com/2016/infrastucture/year-desert-aem-dispatcher/#.Wc7U7VtSxaQ

True.

But dispatcher is not forwarding the requests to AEM instance for child pages.

This is what I am trying to explain. Sorry for any confusion.

The dispatcher is not removing the invalidated files immediately. But when a request for an invalidated file comes, the request will be forwarded to the AEM instance and the response is then used to overwrite the stale file in the dispatcher cache. And then the timestamp is up-to-date (younger than the timestamp of .stat file) and the file is considered fresh again.

Jörg

I understand. 

Whenever I request for these sub-level pages then those are serving from the dispatcher cache (Time stamp of those files are not changing). It suppose to fetch those from publish and replace these invalidated cached files.

So its clearly not invalidating the sub folders.

If you assume "invalidation = removal", then the invalidation is not working. But as I already said, invalidation does not work this way, it does not remove files or complete subdirectories from the cache.