Dispatcher doesn't clear cache after new build | Community
Skip to main content
A
Anonymous
October 16, 2015
Solved

Dispatcher doesn't clear cache after new build

  • October 16, 2015
  • 4 replies
  • 1673 views

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.

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

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

4 replies

Sham_HC
Sham_HC
Level 10
October 16, 2015

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.

A
Anonymous
October 16, 2015

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.

Sham_HC
Sham_HC
Level 10
October 16, 2015

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

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
October 16, 2015

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

Terms & ConditionsAccessibility statement

Loading footer...