Thanks for the prompt reply. We are not setting maxIdle. We are also using an auxiliary disk cache (cache.ccf file is below). Does that mean that when our servers are rebooted, the cache is written to disk and brought back into memory when the server comes back up - so as you say - we NEVER ever refresh the cache once we put something into it?
The documentation mentions the following about Persistance, " When the disk cache is properly shutdown, the memory index is written to disk and the value file is defragmented. When the cache starts up, the disk cache can be configured to read or delete the index file. This provides an unreliable persistence mechanism." Not sure if this is relevant to my question - but does the above support what I think is happening - that the cache is never being refreshed or purged? Also on "When the disk cache is properly shutdown" - how do I "properly" shutdown the disk cache? # DEFAULT CACHE REGION jcs.default=DC jcs.default.cacheattributes=org.apache.jcs.engine.CompositeCacheAttributes jcs.default.cacheattributes.MaxObjects=1000 jcs.default.cacheattributes.MemoryCacheName=org.apache.jcs.engine.memory.lru .LRUMemoryCache # System CACHE REGION jcs.system.groupIdCache=DC jcs.system.groupIdCache.cacheattributes=org.apache.jcs.engine.CompositeCache Attributes jcs.system.groupIdCache.cacheattributes.MaxObjects=10000 jcs.system.groupIdCache.cacheattributes.MemoryCacheName=org.apache.jcs.engin e.memory.lru.LRUMemoryCache # AVAILABLE AUXILIARY CACHES jcs.auxiliary.DC=org.apache.jcs.auxiliary.disk.indexed.IndexedDiskCacheFacto ry jcs.auxiliary.DC.attributes=org.apache.jcs.auxiliary.disk.indexed.IndexedDis kCacheAttributes [EMAIL PROTECTED]@ -----Original Message----- From: James Taylor [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 11, 2003 1:13 PM To: 'Turbine JCS Users List' Subject: Re: MaxLifeSeconds > We have not set the MaxLifeSeconds element attributes. So what is the > Default life of the cache in this case? Infinite, unless maxIdle is set. > My other question is - is there a way to remotely flush the cache? > Maybe using mbeans? Sure, you just need to write an mbean wrapper to do it =] There is a servlet interface for managing the cache, which is what I use. I imagine mbeans could be implemented similarly. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
