PRODUCTS AND SERVICES INDUSTRIES SUPPORT PARTNERS COMMUNITIES ABOUT
  Coherence FAQ
  Why is expiry sometimes initiated later than the configured amount of time?
Added by Joseph Ruzzi, last edited by Joseph Ruzzi on Jun 18, 2009  (view change)

Labels

 

Local caches and backing maps use the <expiry-delay> and <flush-delay> cache configuration elements to configure the amount of time that items may remain in the cache before they expire and the amount of time until expired items are removed from the cache, respectively. Client threads initiate these actions while accessing the cache. This means that the <expiry-delay> and <flush-delay> time may be reached, but not initiated until a client thread accesses the cache. For example, if the <expiry-delay> value is set at 10 seconds (10s) and a client accesses the cache after 15 seconds, then expiry occurs after 15 seconds.

Note

The client thread performs the evictions, not a background thread.