Dispatcher Caching Issues | Community
Skip to main content
Singaiah_Chintalapudi
Singaiah_Chintalapudi
New Participant
September 28, 2017
Solved

Dispatcher Caching Issues

  • September 28, 2017
  • 12 replies
  • 4883 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

Show previous replies
Singaiah_Chintalapudi
Singaiah_ChintalapudiAuthor
New Participant
September 28, 2017

Thanks for the explanation.

If you invalidate the /content/myproject/en/firstlevel/secondlevel/thirdlevel/something.html, it is touching all the .stat files. However, its not invalidating the files in this folder/subfolders.

Please let me know if you need more details.

joerghoh
joerghoh
Employee
September 28, 2017

Hi,

When you have

/content/myproject/en/firstlevel/secondlevel/thirdlevel/fourthlevel/fifthelevel/sixthlevel /child

as path, and have statefilelevel set to 5, it will have 5 levels of .stat files. There will be a statefile at

  • /.stat
  • /content/.stat
  • /content/myproject/.stat
  • /content/myproject/en/.stat
  • /content/myproject/en/firstlevel/.stat
  • /content/myproject/en/firstlevel/secondlevel/.stat

If you will have an invalidation coming it /content/myproject/en/firstlevel/secondlevel/thirdlevel/something.html, it will touch the statfile at /content/myproject/en/firstlevel/secondlevel/.stat, and therefor invalidate all files within this folder and all subfolders. It does not need to have a dedicated stat file at lower levels, because if there is no .stat file in a directory, the dispatcher will look up higher in the hierarchy until it finds a statfile and then compare the timestamps.

So this works as designed.

What is your expectation on flushing? Do you expect that all files in the dispatcher cache are removed, which are flushed? That's not case. Invalidation in the dispatcher just means touching statfiles.

Kind regards,
Jörg

Terms & ConditionsAccessibility statement

Loading footer...