[JCS-161] dynamic regions leak memory upon dispose due to ShrinkerTask

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: jcs-2.0-beta-1
• Fix Version/s: jcs-2.0-beta-2
• Component/s: Composite Cache
• Assignee: Thomas Vandahl
• Reporter: Ryan Fong
• Created: 06/May/16 02:25
• Updated: 25/Dec/16 18:35
• Resolved: 09/May/16 12:09

Description

Creating a dynamic region via JCS.defineRegion and then destroying it via ComposeCacheManager.free does not fully reclaim all memory when the memory shrinker is enabled.

When shrinking is enabled, the org.apache.commons.jcs.engine.memory.shrinking.ShrinkerThread retains a pointer to CompositeCache which is never reclaimed.

A simple solution would be to have org.apache.commons.jcs.engine.control.CompositeCache.setScheduledExecutorService(ScheduledExecutorService) retain the ScheduledFuture as a field. When CompositeCache.disposed is called, we should call ScheduledFuture.cancel.