On 10.03.15 23:12, arnout cator wrote: > Hi, I have the situation that I have 10+ web apps using JCS. I have this in > cache.ccf: > > ################################################################### > # Stylesheet settings > ################################################################### > #disable disk caching if WAS doesn't provide serialized dom > #jcs.region.stylesheet= > jcs.region.stylesheet=DC > jcs.region.stylesheet.cacheattributes.MaxObjects=128 > ################################################################### > > I have no issues with all other regions defined, but I have a problem that > sometimes amongst the 10 web apps, not consistently the same web apps, the > stylesheet cache is not invalidated when I do a code release to the 10 > apps. I get over it by removing all disk cache files and restarting the app > server. > > I wondered if it is possible that JCS sometimes reads the # line. Can that > be causing this?
This is very unlikely because JCS uses the standard JDK methods to read its configuration files. > If not, why would just the stylesheet disk cache file not be invalidated > sometimes? Did anyone in JCS user world see a similar event? I'm not sure I understand your environment correctly. Do you generally expect the cache contents to survive an application restart or not? The disk cache will persist keys and data during an orderly shutdown so that they can be reloaded on restart. This normally requires JCSServletContextListener to be present in the web application. However JCS also registers a shutdown hook to the JVM which may or may not work in an app-server environment. This would explain the inconsistent behavior you are experiencing. Bye, Thomas. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
