Absolutely correct. It's fixed in my latest build, and will go in with the rest of my updates to CompositeCache when I get commit access.
Even more reinforcement of my prior wish list for tests for element expiration and idling. -Travis Savo -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, April 05, 2004 11:14 PM To: Turbine JCS Users List Subject: Bug in Cache Element Removal when its expired When Cache Element is expired in Memory, it should be removed from Map object, which contains all cache elements. But it doesn't happen. and I found the cause of it. Here is the code in CompositeCache which tries to remove cache item if it is expired: protected ICacheElement get( Serializable key, boolean localOnly ) { ............................................. if ( isExpired( element ) ) { if ( log.isDebugEnabled() ) { log.debug( cacheName + " - Memory cache hit, but element expired" ); } missCountExpired++; remove( element ); element = null; } else { ....................................... } remove(element) doens't work as here key needs to be passed not the entire element. Can anybody fix it and release it along with disk caching fixes? **************************************************************************** ***** Important Note This email (including any attachments) contains information which is confidential and may be subject to legal privilege. If you are not the intended recipient you must not use, distribute or copy this email. If you have received this email in error please notify the sender immediately and delete this email. Any views expressed in this email are not necessarily the views of AXA. Thank you. **************************************************************************** ***** --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
