nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

LSDS 7.3.1 caching issue

Rohan_t1

We recently migrated from 6.7.2 SP1 to TS 7.3.1.

We see caching issue at runtime where the template within the page is cached across multilingual sites. This would result in sites displaying cached content across sites regardless of the locale. The related default.site, default.sitemap and landing pages are deployed for each locale but we still see the content of recent deployed locale. Interesting part being components not part of template display latest content but the ones within the template display cached content.

All the components are set with the setting of "Until Published". I tried changing them to No Cache which resolves the issue. So i am guessing it is a config change which needs to be done to fix the issue? Has any one encountered this issue before?

The xxxxxx.cache files deployed get clean up fine so looks like there is no issue with basic cache invalidation process. Any thoughts?

Find more posts tagged with

Comments

Rohan_t1

I enabled the logger to see if i can find any error. Nothing interesting except:

DEBUG [com.interwoven.livesite.runtime.cache.InvalidationMonitor] run: checking for cache files /xxxx/iw-runtime/app/iw-runtime/sites
DEBUG [com.interwoven.livesite.runtime.cache.InvalidationMonitor] File is older that last invalidation(Tue Jan 17 14:26:54 GMT 2012) file time: Tue Jan 17 14:26:54 GMT 2012 /xxxx/iw-runtime/app/iw-runtime/sites/cache.8q6evgudhnf4uu412
DEBUG [com.interwoven.livesite.runtime.cache.InvalidationMonitor] run: checking for cache files /xxxx/iw-runtime/app/iw-runtime/sites
DEBUG [com.interwoven.livesite.runtime.cache.InvalidationMonitor] File is older that last invalidation(Tue Jan 17 14:26:54 GMT 2012) file time: Tue Jan 17 14:26:54 GMT 2012 /xxxx/iw-runtime/app/iw-runtime/sites/cache.8q6evgudhnf4uu412
DEBUG [com.interwoven.livesite.runtime.cache.InvalidationMonitor] run: checking for cache files /xxxx/iw-runtime/app/iw-runtime/sites
DEBUG [com.interwoven.livesite.runtime.cache.InvalidationMonitor] File is older that last invalidation(Tue Jan 17 14:26:54 GMT 2012) file time: Tue Jan 17 14:26:54 GMT 2012 /xxxx/iw-runtime/app/iw-runtime/sites/cache.8q6evgudhnf4uu412
DEBUG [com.interwoven.livesite.runtime.cache.InvalidationMonitor] run: checking for cache files /xxxx/iw-runtime/app/iw-runtime/sites

Although it is set to check for cache files every 30 secs..It actually takes 20 mins to do so. Not sure if it is related to the original issue.

nipper

Talk to support. There are some issues with the caching of dynamic content (reading contrent from DCRs or from LSCS) in 7.2.1, they still may be a problem in 7.3.1. In our case we had to restart the app server to get changes to show. Smiley Sad

We ended up having to write some custom java to get around it.

Crsb

are you using any kind of site/page controller? if you do, does the cache behave differently when you have different logging levels?

Rohan_t1

Talk to support. There are some issues with the caching of dynamic content (reading contrent from DCRs or from LSCS) in 7.2.1, they still may be a problem in 7.3.1. In our case we had to restart the app server to get changes to show.

We ended up having to write some custom java to get around it.

Thanks Nipper. Raising the case with Support now. When you have time can you check if you can go to http::/server-name Smiley Tongue

ort/iw/admin/JCS.jsp

I seem to be getting compilation errors. Looks like it is looking for com.interwoven.livesite.runtime.cache.CompressedCacheData <%@ page import="com.interwoven.livesite.runtime.cache.CompressedCacheData" %>and failing. I looked into livesite.runtime.jar to see if this class exist but i couldn't find one under com.interwoven.livesite.runtime.cache. Can you confirm if the above link works ok? If yes..JCS.jsp under iw-runtime/app/iw-runtime/iw/admin has this import reference?

Rohan_t1

are you using any kind of site/page controller? if you do, does the cache behave differently when you have different logging levels?

We don't use any controllers. We just have external which is the only customization. Just trying to get the basic things running first Smiley Happy

nipper

Thanks Nipper. Raising the case with Support now. When you have time can you check if you can go to http::/server-nameort/iw/admin/JCS.jsp

I seem to be getting compilation errors. Looks like it is looking for com.interwoven.livesite.runtime.cache.CompressedCacheData <%@ page import="com.interwoven.livesite.runtime.cache.CompressedCacheData" %>and failing. I looked into livesite.runtime.jar to see if this class exist but i couldn't find one under com.interwoven.livesite.runtime.cache. Can you confirm if the above link works ok? If yes..JCS.jsp under iw-runtime/app/iw-runtime/iw/admin has this import reference?

Sorry, on a different project now, do not have access to that system anymore.

Crsb

We don't use any controllers. We just have external which is the only customization. Just trying to get the basic things running first

do you have any logging messages from those externals? I had a cache issue before where I had to have at least one info message in page controller for page tokens to get updated. if I had no logging messages in my custom code where the page tokens are getting updated, the page was serving cached version of what was supposed to be dynamic.

tec_iwov

do mean page template or xsl template.

we cache the page layout in the page cache (inle refreshed on publish or invalidation)

in component cache we cache the rendered content of the component based on a key that contains site page and component IDs along with segment and locale.

does your external have parameters? we use the defined parameters to determine what request parameters the external will use and build a checksum that is also used as part of the key.

also logging or changing logging levels does not effect how things get cached.

Rohan_t1

do mean page template or xsl template.

we cache the page layout in the page cache (inle refreshed on publish or invalidation)

in component cache we cache the rendered content of the component based on a key that contains site page and component IDs along with segment and locale.

does your external have parameters? we use the defined parameters to determine what request parameters the external will use and build a checksum that is also used as part of the key.

also logging or changing logging levels does not effect how things get cached.

Sorry for the delay in reply. Yes i meant page template being cached across locales. We haven't saw in any issues with external yet but still face the caching issue. We raised this with support and they have been able to replicate the issue. Awaiting their further response.