commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sahib Bin Mahboob Ron <sa...@cefalo.com>
Subject JCS : element expires sooner than configured
Date Mon, 23 Jan 2017 09:48:25 GMT
Hi,

I am trying to configure a JCS using the following configuration:

# DEFAULT CACHE REGION

jcs.default=
jcs.default.cacheattributes=
    org.apache.commons.jcs.engine.CompositeCacheAttributes
jcs.default.cacheattributes.MaxObjects=1000
jcs.default.cacheattributes.MemoryCacheName=
    org.apache.commons.jcs.engine.memory.lru.LRUMemoryCache

jcs.default.elementattributes=org.apache.commons.jcs.engine.ElementAttributes
jcs.default.elementattributes.IsEternal=false
jcs.default.elementattributes.MaxLife=300
jcs.default.elementattributes.IsSpool=false


While it is expected to expire the item in 300 seconds as per MaxLife
configuration, it does not work properly in following steps:

1. Putting a key "aKey" for the first time in cache: It works perfectly.
2. "aKey" expires after 300 seconds.
3. Put "aKey" again on the cache.
4. It expires immediately.

Am I missing any configuration or this is the way it should behave?

- Sahib

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message