Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Sat, 28 Jan 2012 16:45:09 +0000 (UTC)
From: "Diego Rivera (Created) (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: 
 <440137508.4599.1327769109981.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (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.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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
         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