• Bug
  • Status: Closed
  • Resolution: Fixed
  • drb
  • Reporter: sourceforgetracker
  • September 21, 2009
  • 0
  • Watchers: 0
  • September 22, 2009
  • September 22, 2009


I register CacheEventListener on EHCache in order to get notification about expiry of the element. I have low time to idle set to 10 sec. I put an element and wait longer than 10 sec and do not see notifyElementExpired() called. When I do a get on the element after a long time, it tells me it was not found and it fires notifyElementExpired at that time.

I am looking for a Java cache that will give me real time notification of expiry. Is this a bug or a intentional design of EHCache? Can it be modified with configuration parameter.


Jacek Korycki Sourceforge Ticket ID: 2649377 - Opened By: korycki - 28 Feb 2009 19:06 UTC


Sourceforge Tracker 2009-09-21


I think we exchanged email on this. Element expiry is lazy, but you can create a CacheExtension which will regularly iterate through the cache, thus triggering expiries. That will work for you implementation.

As this is an intentional design feature I will close this bug.

Greg Comment by: gregluck - 1 Apr 2009 07:03 UTC

Fiona OShea 2009-09-22

Re-opening so that I can properly close out these issues and have correct Resolution status in Jira