Solved

AEM Cloud Dispatcher Cache

Forum|Forum|2 years ago
January 18, 2024
6 replies
2584 views

We are facing one issue on AEM Cloud, publishing XF is not working on publisher/dispatcher instance - they are still referring old XF and showing old XF content on a page.

Problem:

We are using XF/Experience Fragments included in template for Header and footer. Header and Footer XF are included in the template structure. XF are not getting updated on the pages since the content pages are cached with header and footer html’s as part of the pages. So only updating the XF wont invalidate the pages. The entire content hierarchy would need to be invalidated to see the updated XF content on pages.

My questions are

How to rectify this issue?
Do we need to explicitly invalidate dispatcher/CDN cache? If yes how?
Why the cache is hanging on it the old content for so long?

I know about SDI can be implemented here to resolve this but we don't want to include ACS Commons for AEM cloud.

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 yashp0808

Hi @gatsby,

First option you have is to publish the pages where the XFs are included and that should invalidate the cache.

If manually publishing the content tree is not feasible, you can create a custom Event listener to publish the pages where the XF is being included on publish of the XF.

Another option is to open a support ticket with Adobe and request cache flush(not recommended).

Also, are you sure its cached on dispatcher or is the cache not validated on Fastly? If it is fastly, you can request Adobe to provide you with a Flush key for the environment and then setup a cURL based job to invalidate fastly cache.

kapil_rajoria

Community Advisor

Hi @gatsby , this seems to a common issue that you are facing. We always have to manually clear the dispatcher cache by going into miscadmin every time when there are changes related to xml or content on a page and there is a new deployment. To clear the dispatcher cache you can follow the steps mentioned in this:
https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/page-invalidate.html

Still if you are seeing your old page, try passing an empty parameter in your URL and hit enter. For Eg: <your URL>?p=0
By this way, you can make sure the fresh content loads and not the cached content.

To programmatically clear the dispatcher cache please visit:
https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/flush-dispatcher-cache-programmatically-in-aem-as-cloud-service/td-p/463312

Why the cache is hanging on it the old content for so long?
Cache helps in loading the pages faster so they need to be manually cleared just like in browsers.

Jagadeesh_Prakash

Community Advisor

@gatsby We have similar issue for one of our clients. Where we followed below steps

1. And EventHandler with below properties

@Component(immediate = true, property = { "event.topics=org/apache/sling/distribution/importer/package/imported",
       "event.filter=(|(distribution.type=ADD)(distribution.type=DELETE))" })

2. And We prepare list of pages that refer the XF and preparing purgeListObject

3. And did a cache clear for those particular pages.

In a way you can also write a servlet which can do this manually as well.

G

GatsbyAuthor

@jagadeesh_prakash I like this idea, but this could be performance issue when you clear cache, especially header footer I'll be using on each page, so clearing cache for all those pages leads to performance issue.

yashp0808Accepted solution

Hi @gatsby,

First option you have is to publish the pages where the XFs are included and that should invalidate the cache.

If manually publishing the content tree is not feasible, you can create a custom Event listener to publish the pages where the XF is being included on publish of the XF.

Another option is to open a support ticket with Adobe and request cache flush(not recommended).

Also, are you sure its cached on dispatcher or is the cache not validated on Fastly? If it is fastly, you can request Adobe to provide you with a Flush key for the environment and then setup a cURL based job to invalidate fastly cache.

K

KNan

Community Advisor

Hi @gatsby

The dispatcher flush listeners are activated when a replication or publish request is initiated. In your scenario, as there is no activation, the dispatcher flush is not triggered. To update the cache, you either need to publish the page after making XF changes or implement custom listeners.

please read this

Efficiently Caching : Experience Fragments on dispatcher

Thanks

Kannan

Sudheer_Sundalam

Community Advisor

@gatsby ,

Please take look at this community posted related to flushing pages on activation of the Experience Fragments.

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/experience-fragment-caching/td-p/639063

kautuk_sahni

Community Manager

@gatsby Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

Kautuk Sahni

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded