Is there a way to configure CQ such that modifying a page directly on a publisher instance invalidates it from the dispatcher cache? | Community
Skip to main content
LinearGradient
LinearGradient
Level 6
October 16, 2015
Solved

Is there a way to configure CQ such that modifying a page directly on a publisher instance invalidates it from the dispatcher cache?

  • October 16, 2015
  • 2 replies
  • 955 views

Hi,

I have a job that runs on all publisher instances and continuously touches some pages (it modifies their cq:lastModified and cq:lastModifiedBy properties). I was expecting the pages to be invalidates from the dispatcher cache as a consequence of this, but they are not.

Of course I can modify the pages on the author and activate them, but is there a way to achieve this directly on the publisher instances without having to activate content from author to publishers first?

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 Abhinav_Sap
        You can write a event listener service, which is run mode aware. You can can listen to relevant jcr events and trigger content flush from publish. You'll have to setup flush agent on publish .instances.

2 replies

Lokesh_Shivalingaiah
Lokesh_Shivalingaiah
Level 10
October 16, 2015

Hi,

Ideally we shouldnot be changing anything directly on the publish instance. Perfect would be to update in the author and activate them. 

But, if it has to be done then, you will have to write a code to invalidate cache 

A
Abhinav_SapAccepted solution
Level 2
October 16, 2015
        You can write a event listener service, which is run mode aware. You can can listen to relevant jcr events and trigger content flush from publish. You'll have to setup flush agent on publish .instances.
Terms & ConditionsAccessibility statement

Loading footer...