Affects Version/s: jcs-1.3
Fix Version/s: jcs-2.0-beta-1
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.
|Assignee||Thomas Vandahl [ tv ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Fix Version/s||jcs-1.4-dev [ 12312535 ]|
|Resolution||Fixed [ 1 ]|
|Status||Resolved [ 5 ]||Closed [ 6 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|64d 18h 54m||1||Thomas Vandahl||02/Apr/12 12:38|
|1094d 3h 12m||1||Thomas Vandahl||01/Apr/15 15:50|