Keith Wall created QPID-4271:
--------------------------------

             Summary: Avoid ThreadLocal leakage etc at shutdown so that Broker 
behaves better when embedded within Containers
                 Key: QPID-4271
                 URL: https://issues.apache.org/jira/browse/QPID-4271
             Project: Qpid
          Issue Type: Bug
          Components: Java Broker
            Reporter: Keith Wall
             Fix For: 0.19


Some customers are embedding the Java Broker within application containers such 
as Tomcat.

Successive undeploy/redeploy of the component shows warnings highlighting 
potential ThreadLocal leaks on Container owned threads.  For instance, Tomcat 
reports:

{noformat}
SEVERE: The web application [/qpid-0.19] created a ThreadLocal with key of type 
[org.apache.qpid.server.logging.actors.CurrentActor$1] (value 
[org.apache.qpid.server.logging.actors.CurrentActor$1@661eef2c]) and a value of 
type [java.util.Stack] (value [[]]) but failed to remove it when the web 
application was stopped. Threads are going to be renewed over time to try and 
avoid a probable memory leak.
SEVERE: The web application [/qpid-0.19] created a ThreadLocal with key of type 
[org.apache.qpid.framing.AMQShortString$1] (value 
[org.apache.qpid.framing.AMQShortString$1@7382ab3e]) and a value of type 
[org.apache.qpid.framing.AMQShortString$1$1] (value [{queue=queue, ping=ping, 
test-ping=test-ping, test-queue=test-queue}]) but failed to remove it when the 
web application was stopped. Threads are going to be renewed over time to try 
and avoid a probable memory leak.
Aug 28, 2012 4:05:16 PM org.apache.catalina.loader.WebappClassLoader 
checkThreadLocalMapForLeaks
{noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to