Invalidate Runtime Cache

Hi,

When I publish my .page to runtime, I can't see the updated contents until I select Invalidate Runtime Cache.

I read that we can create cache.**** file to be deployed together with the .page? Are there any other way to modify the page cache everytime it gets published?

Btw I'm using TS, LS, OD & SP 7.0

Thanks

Find more posts tagged with

Comments

srosewall

Are there any other way to modify the page cache everytime it gets published?

You could use the out-of-the-box Publish LiveSite Content (PLC) workflow to publish your pages/content.
That includes the creation and deployment of a cache invalidation file for LSDS to process.
When this is received it is used by JCS (Java Caching System which LiveSite uses to cache objects) to remove objects from the cache.
LSDS regularly checks for the presence of a cache file, and when it finds one, uses it to invalidate the cache.

The "Invalidate Runtime Cache" option uses the same method to perform the cache clearing for you.

Alternatively, you would need to programatically create a cache file and ensure that it is deployed to the runtime as part of your deployment of pages/content to LSDS.

A cache file needs to be deployed to the root of the runtime target deployment folder stucture to be used, and should contain a list of files which have been deployed (relative paths).
For exact details, use the "Invalidate Runtime Cache" option or the PLC to create a cache file, and examine the contents - you will need to be quick as the cache file is deleted once used, or you could stop LSDS so that it doesn't process the cache file.

Hope that helps.

jihan

Hi srosewall,

Thanks for the info. I'm not using PLC workflow, so that's why we're using the Invalidate Runtime Cache command.

So does this means there's no other way of clearing the cache other than the method u just explained?

Thanks

srosewall

So does this means there's no other way of clearing the cache other than the method u just explained?

Your only other option is to use the JCS admin web page -

http://hostname: portnumber/iw/admin/JCS.jsp

Regards

jihan

Hostname should be my runtime server's hostname, right? I tried with the url given but I still can't see my updated content. Anyway, if I have 3 runtime servers means this way I've to clear the cache from the 3 servers' JCS admin. I don't think this will do..

So this means the only way I can clear the cache is by creating it and deploy with my custom workflow. How do I create the cache.**** file?

Btw, any config at any place possible that I can set to clear the cache for every hour or something?

srosewall

Hostname is your LSDS server name
Port is your LSDS port

You need to click on the clear cache options presented to you to invalidate the cache.

Cache file create: too generalised a question to be able to answer - could be Perl script / Java class etc.

Configuration: you can specify on a component level when the cache should be invalidated - see developers guide for details.

Regards

Adam Stoller

I'm not working with LS (haven't really done so thus far) and I don't know the full details of the cache file - but based on your (srosewall) responses, it sounds like a target-side DNR script to create a target-area-relative-path file list of the files which were successfully deployed would be a fairly straight-forward approach to creating the file. As you (again srosewall) suggest - temporarily disabling LSDS and using the OOTB PLC workflow to get a working example of the cache file's contents and format would be the best first-step, then create a DNR script using that information to do so for your (jihan's) implementation sounds like the way to go. It doesn't sound that complicated - probably 1-2 hours worth of work at the most.

jihan

Hi all,

Thanks for your reply. So I'll try to create the cache.**** file then. Btw, I tried to run Invalidate Runtime Cache to see the content of the cache file. All I see is the page name. Is this correct? And this cache file should be deployed to /sites folder, correct?

Thanks!

jihan

Hi,

Apart from workflow, can I set the cache to be No Cache? Or probably make the Invalidate Runtime Cache funtion to run automatically every hour?

sampleReport.rptdesign

kgilmore

We had a similar caching issue in LS 7.1 that appeared yesterday. A component dependent on a DCR was not being refreshed after updating and republishing the DCR. The component was set to cache "until published". I used the JCS Admin Servlet to clear the component cache, and then the changes appeared on the runtime server.

jihan

Hi kgilmore,

I did try to use the JCS Admin page and it works, but in our case we have 4 runtime servers and the publishing of page occurs very often everyday.

So I did the cache deploy with workflow. So far in my staging env it works fine, but now wondering if there's a setting in LiveSite for the cache to be cleared every hour or so?

srosewall

...but now wondering if there's a setting in LiveSite for the cache to be cleared every hour or so?

There's no global setting in the LiveSite application (so nothing like cache=true|false).

You might be able to change the behaviour of JCS - you would need to consult the documentation for it which is available on-line (it's an open source caching solution and has a control file called cache.ccf).

Or you could set the cache interval on the components on your pages that you want to be refreshed on a regular basis.
I'd suggest this as being your best option.

Regards,
Stuart

tec_iwov

you should turn on debug logging on your runtime to see why the cache is not getting flushed. There are predefined categories for this in log4j.xml

The JCS admin page is for troubleshooting only it is not intended for cache invalidation.

IF your using the PLC workflow this will generate the cache invalidation file for you. if not you will need to do this in add it to the deployment manifest so that it is place in the root of the sites dir on your runtime system.

currently as mentioned you need to use the cache invalidation menu item to reset a page if it's dependencies have changed. functionality is being added now the dependency management is in place to do this as part of deployment as well.

jihan

Hi all,

I didn't modify the JCS' cache.ccf, since for now the cache invalidation file deployed in the runtime sites folder is working fine.

I'm still monitoring it though. I'll turn on debug and consult the JCS documentation in case of any tuning required.

Thanks for all the advise!

jihan

Hi,

I've implemented the cache.**** file deployment, and from what I see, in our runtime server, it doesn't delete the cache file.

Is this behavior normal? If it's not deleted, then every time the Invalidation Monitor runs, it will read through all of the cache.**** file and try to clear again, right? Will this be an issue with the memory/cpu usage of the server?

Thanks

tec_iwov

the file doesn't get deleted immediately. we have a feature where the sites dir can be shared by multiple runtimes. if you turn on debug logging you can see what processing is being done.

jihan

Hi there,

Thanks for the help. Found out the cause was folder permission. Changed it, and now it works fine. CPU usage is back to normal. At least for now. Will keep monitoring tho.

Thanks!