Dispatcher Caching Issues | Community
Skip to main content
Singaiah_Chintalapudi
Level 7
September 28, 2017
Solved

Dispatcher Caching Issues

  • September 28, 2017
  • 12 replies
  • 4898 views

We set the /statfileslevel to 5.

Issue 1:

content tree:  /content/myproject/en/firstlevel/secondlevel/thirdlevel/fourthlevel/fifthelevel/sixthlevel/child pages

If I activate the fourthlevel page, it is invalidating the fourthlevel page and its parent pages (until secondlevel). Because our /statefile is set 5 and it is touching all of these .stat files upon page activation. It is not flushing the /fifthelevel/sixthlevel/child pages.

But adobe documentation shows it will flush the bottom pages not the top pages.

Issue 2:

We have a iParsys on sixthlevel. Whenever we update any content on iParsys and publish the sixthlevel page, it is flushing only the sixth level page not the child pages which are inheriting the sixthlevel content. So we had to manually flush the cache.

Based on this thread, it should flush the all child pages.

https://forums.adobe.com/thread/2339221

Thanks.

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 joerghoh

Hi,

ah, that's a different story then. Set the dispatcher loglevel to "3", restart the dispatcher, execute one of the requests which are not forwarded to AEM and provide us with the relevant part of the logfile then.

Jörg

12 replies

joerghoh
Adobe Employee
Adobe Employee
October 13, 2017

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

Singaiah_Chintalapudi
Level 7
October 13, 2017

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