what exactly is cache time and its usage in Component?

Hi,

While creating component what is the significance of cache time, by the name i can understand that it shud refresh page i.e. hits the server at particular time.
But I have following queries:

1) Does hitting the server means to give Ajax call to server?

2) What if I select Never cache? because I have analyzed that while creating the component If i didn't select this option, My page behaves abnormally like let's say my page is having 5 links and on each click of link the body of page should display the content related to that link. But when I click on another link it never change the content of page on single lick, i have to click two to three times and then it redirects the page to different link.Is it because of cache?

3)What if I select Untill Published?

Which option should use and when? and what are the pros and cons of selecting this option.

Kindly elaborate with examples

Thanks in advance.

Find more posts tagged with

Comments

vpatel

Hi,

While creating component what is the significance of cache time, by the name i can understand that it shud refresh page i.e. hits the server at particular time.
But I have following queries:

1) Does hitting the server means to give Ajax call to server?

2) What if I select Never cache? because I have analyzed that while creating the component If i didn't select this option, My page behaves abnormally like let's say my page is having 5 links and on each click of link the body of page should display the content related to that link. But when I click on another link it never change the content of page on single lick, i have to click two to three times and then it redirects the page to different link.Is it because of cache?

3)What if I select Untill Published?

Which option should use and when? and what are the pros and cons of selecting this option.

Kindly elaborate with examples

Thanks in advance.

Cache time basically means how frequently your component should be refreshed. Let's say you set it to 1 hour then your component's content would be cached every 1 hour (or whenever the next request comes in once it has expired) and it would not be any more than 1 hour old.

If you set it to until publish then the component content will be refreshed only when you republish that page. This is ideal for pages that don't change unless you explicitly re-publish that page.

If you set it to no caching then your component is NOT cached at all. This is expensive. Having a component cache down to 1 minute will probably give you far better performance than not caching it at all. You should cache as many components as possible for as long as possible.

HTH!

SE123

Thanks for your reply,

But I am facing one problem in my project, I want my page to be refreshed only when I republish the page. But let's say if I made some changes in component and update the page with latest component and republish the page my changes are not getting reflected and it takes the same page which was generated on first hit of request. To get rid of this problem we need to first rename the page and then we have to publish the page. In this scenario also we were able to access the page which we have deleted recently that means the page is still there in cache. How can we avoid this? While creating component we have to set the property as No Cache for proper functioning.

vpatel

Thanks for your reply,

But I am facing one problem in my project, I want my page to be refreshed only when I republish the page. But let's say if I made some changes in component and update the page with latest component and republish the page my changes are not getting reflected and it takes the same page which was generated on first hit of request. To get rid of this problem we need to first rename the page and then we have to publish the page. In this scenario also we were able to access the page which we have deleted recently that means the page is still there in cache. How can we avoid this? While creating component we have to set the property as No Cache for proper functioning.

There may be some latency in refreshing the cache with the *on-publish*. I believe that is usually about 30 seconds or so. Perhaps LS is not processing the cache files correctly. Look at your production LS Runtime logs and make sure the cache files are being processed correctly for one and for two make sure there are no apparent errors.

SE123

There may be some latency in refreshing the cache with the *on-publish*. I believe that is usually about 30 seconds or so. Perhaps LS is not processing the cache files correctly. Look at your production LS Runtime logs and make sure the cache files are being processed correctly for one and for two make sure there are no apparent errors.

Could you please elaborate where can I find the LS Runtime logs and whether they are processing correctly or not? As of now I am referring the catalina.out logs which are generated in tomcat instance.
I'll tell you one more strange scenario where I have explicitly deleted the page from my Front Office server i.e. tomcat instance and when I hit the page again I was able to access the page.

Then I deleted all the directories under Tomcat/work and tried the option but I was able to access the page.

After that I restarted the tomcat instance and tried to access the page then I got the no page found error which was expected.

But when I republish the page from Back Office server with some changes in the component. Again my changes were not gets reflected at Front Office server and the same page appears which I got at the first hit of my request.

Let me know if you require any more details.

tec_iwov

What version of Livesite are you running?

Are you using the Livesite workflow (PLC) or do you have a custom workflow?

There is a livesite.runtime.log that should be located at the same location as the catalina logs.

there's a log4j.xml configuration file in the web-inf/classes folder of the runtime. IT should have some canned categories that you can enable to see cache processing.

SE123

What version of Livesite are you running?

Are you using the Livesite workflow (PLC) or do you have a custom workflow?

There is a livesite.runtime.log that should be located at the same location as the catalina logs.

there's a log4j.xml configuration file in the web-inf/classes folder of the runtime. IT should have some canned categories that you can enable to see cache processing.

I am using Livesite 3.0 version. We have custom Workflow to deploy the files from one branch to the same branch but present on Front Office server which is mapped to a separate Tomcat Instance. Like say if we have 3 branches then there will be three different tomcat instances available on Front Office server.

I have checked under logs folder where my catalina.out is generated but i didn't find livesite.runtime.log there. Also, I have checked the log4j.xml where I found only the entry of enduser.log (don't know what is its usage) but theer were no entry for cache related log or processing.

vpatel

I am using Livesite 3.0 version. We have custom Workflow to deploy the files from one branch to the same branch but present on Front Office server which is mapped to a separate Tomcat Instance.

Who developed this WF? Did they build the functionality in this WF to clear the cache when files are deployed? You should look into that first.

tec_iwov

enduser.log is the base log for all livesite runtime logging.

that will be the one you need to check for cache logging.

As vpatel stated you should determine if your custom workflow is generating
the cach invalidation files. you should contact support if it is not.

Also what flavor of workflow? As of 3.0 LS only supports the workflow modeler and java based workflows. we do not actively update the perl workflow.

these are the entries you will need to see if cache is functioning properly:
[html]

[/html]