Not able to invalidate JSON in dispatchers | Community
Skip to main content
Level 5
March 16, 2016

Not able to invalidate JSON in dispatchers

  • March 16, 2016
  • 2 replies
  • 9871 views

As per our requirements we are caching the pages in dispatcher  like this format ex :- /content/eacom0/en_us/help/Sam_Test_Availability_Alpha_Beta_Demo/jcr:content.-1.json .

The problem here is I am not able to invalidating the jcr:content.-1.json by using the dispatcher configurations.

Any suggestions or solutions for this. 

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.

2 replies

dragon2AAuthor
Level 5
March 16, 2016

I have tried everything except the sling Servlet.

Does there any way to handle via the configurations instead of the servlet. ?

joerghoh
Adobe Employee
Adobe Employee
March 16, 2016

What do you mean with "I am not able to invalidate ..."? What have you tried? Can you set the dispatcher on loglevel DEBUG and post the relevant logs then?

Kind regards,
Jörg

dragon2AAuthor
Level 5
March 17, 2016

We are caching the pages using JSON format like this /jcr:content.-1.json .

After publishing of the page , we are able to cache dispatcher but when we do modifications and reactivated the page it suppose to clean that cache at the time of reactivation (by using the triggers in publisher agents).

But what is happening its not invalidating/clearing the cached JSON in dispatcher , The result is we are unable to get the latest changes . We always getting the first one.

With same configurations We are able to invalidate the .html in dispatcher after the reactivation of the pages.

I hope you understand the situation :)

Ashokkumar_TA
Level 2
March 17, 2016

Can you share the /invalidate section of your dispatcher.any configuration and the dispatcher log entries...