[JCS-90] When issuing a shutDown() command, JCS fails to clean up the Queue Processor thread. This can lead to thread leakage in an environment where webapps are hot-deployed and hot-undeployed.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: jcs-1.3
• Fix Version/s: jcs-2.0-beta-1
• Assignee: Thomas Vandahl
• Reporter: Diego Rivera
• Created: 28/Jan/12 16:43
• Updated: 01/Apr/15 14:50
• Resolved: 02/Apr/12 11:38

Description

When a shutDown() command is issued to CompositeCacheManager, the the CompositeCache.eventProcessorQ thread is not disposed of, leading to thread leakage in environments where the JVM doesn't exit immediately after issuing the shutdown. This is the case in environments where web applications are hot-deployed or hot-undeployed.

Similarly, the "graceful termination" implemented utilizes Thread.destroy(), which was never implemented, so there's nothing graceful about a NoSuchMethodError(). This has been changed to be a truly graceful exit (i.e. break out of the loop so that the method can return cleanly).

A patch to fix will be attached shortly.