Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED
Invalidation is not happening while triggerring the flush request for custom servlet through code
1 Accepted Solution
Correct answer by
Based on the logs you provided, it seems that the resource-only-flush request was successful and the invalidation request was received by the dispatcher. However, it's possible that the cached JSON files for all countries were not cleared because the invalidation request was not specific enough.
When you trigger a resource-only-flush request for `/bin/myproject/servlet`, it invalidates the cache for that specific path only. It does not invalidate the cache for any child paths or any other paths that may be related to the servlet.
To clear the cached JSON files for all countries, you may need to trigger a resource-only-flush request for each country-specific path, such as `/bin/myproject/servlet/us/en/myservlet.json`, `/bin/myproject/servlet/uk/en/myservlet.json`, etc. This will ensure that the cache for each country-specific path is cleared and the updated JSON files are served from the publish instance.
Alternatively, you can trigger a full cache flush on the dispatcher to clear all cached content. However, this may not be desirable if you have a large amount of cached content or if you want to minimize the impact on the dispatcher performance.
Thanks,
Raja
Correct answer by
Based on the logs you provided, it seems that the resource-only-flush request was successful and the invalidation request was received by the dispatcher. However, it's possible that the cached JSON files for all countries were not cleared because the invalidation request was not specific enough.
When you trigger a resource-only-flush request for `/bin/myproject/servlet`, it invalidates the cache for that specific path only. It does not invalidate the cache for any child paths or any other paths that may be related to the servlet.
To clear the cached JSON files for all countries, you may need to trigger a resource-only-flush request for each country-specific path, such as `/bin/myproject/servlet/us/en/myservlet.json`, `/bin/myproject/servlet/uk/en/myservlet.json`, etc. This will ensure that the cache for each country-specific path is cleared and the updated JSON files are served from the publish instance.
Alternatively, you can trigger a full cache flush on the dispatcher to clear all cached content. However, this may not be desirable if you have a large amount of cached content or if you want to minimize the impact on the dispatcher performance.
Thanks,
Raja
Related Conversations
