-
Bug
-
Resolution: Obsolete
-
Major
-
None
-
5.2.6.Final
When adding an entry to the cache (embedded), specifying maxIdle... The entry goes into the store, but the store removes the entry when maxIdle time elapses from creation (rather than from last access).
The cache correctly keeps the entry in memory (unless evicted).
This leaves the cache and store out of sync.
I saw this same behavior with both stringKeyedJdbcStore and fileStore.
- is related to
-
ISPN-9003 Clustered maxIdle expiration
- Closed