Expand my Community achievements bar.

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

Dispatcher doesn't clear cache after new build

Avatar

Former Community Member

Hi,

We are facing issue related to dispatcher cache. Sometimes, even after fresh build, files in htdocs are not updated and we need to run /dispatcher/invalidate.cache manually.

The problem is when we do a new code deployment, the javascript files if get changed are not getting cleared in dispatcher cache. Do we have versioning number so that the enduser browser cache or dispatcher cache gets updated if it finds a new one?

Or ss there a way to make sure UI libraries and other files in htdocs are updated after the new build is deployed.

Thanks in advance.

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

It's probably easiest, if you schedule a purge via cron on your DEV environment. IIRC the replication agents are triggered only by changes of pages and assets, if you configure them to start "on modification".

Kind regards;
Jörg

View solution in original post

4 Replies

Avatar

Level 10

In invalidate section of dispatcher.any need to allow for library.  It is recommended to clear a cache manually on code deploy if there are many changes since it is one time.

Avatar

Former Community Member

Hi Sham,

We do have entries in invalidate section of dispatcher.any. However, on our test environment we do daily code deploy and we face this issue regularly. Is there any other way to force invalidation every time we do a code deploy.

Avatar

Level 10

PJindal wrote...

Hi Sham,

We do have entries in invalidate section of dispatcher.any. However, on our test environment we do daily code deploy and we face this issue regularly. Is there any other way to force invalidation every time we do a code deploy.

 

use dispatcher pre-population feature by consisting of linefeed separated URLs that the dispatcher should automatically refetch OR

write an invalid script to delete using invalidateHandler. http://docs.adobe.com/docs/en/dispatcher/disp-config.html

Avatar

Correct answer by
Employee Advisor

It's probably easiest, if you schedule a purge via cron on your DEV environment. IIRC the replication agents are triggered only by changes of pages and assets, if you configure them to start "on modification".

Kind regards;
Jörg