You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Thomas Vandahl (Resolved) (JIRA)" <ji...@apache.org> on 2012/04/02 13:39:22 UTC

[jira] [Resolved] (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.

     [ https://issues.apache.org/jira/browse/JCS-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Vandahl resolved JCS-90.
-------------------------------

       Resolution: Fixed
    Fix Version/s: jcs-1.4-dev

Modified fix applied.
                
> 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.
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JCS-90
>                 URL: https://issues.apache.org/jira/browse/JCS-90
>             Project: Commons JCS
>          Issue Type: Bug
>    Affects Versions: jcs-1.3
>            Reporter: Diego Rivera
>            Assignee: Thomas Vandahl
>             Fix For: jcs-1.4-dev
>
>         Attachments: jcs-90-fix.patch
>
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira