activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] [Commented] (AMQ-4008) Tomcat WARN on shutdown about ThreadLocal not cleared from log4j
Date Fri, 31 Aug 2012 09:12:07 GMT


Claus Ibsen commented on AMQ-4008:

Fixed the MDC leak reported by Tomcat. 

Now hunting another issue when embedding Camel together and routing messages

Aug 31, 2012 11:13:35 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/camel-example-activemq-tomcat] appears to have started a thread
named [ActiveMQ Task-1] but has failed to stop it. This is very likely to create a memory
> Tomcat WARN on shutdown about ThreadLocal not cleared from log4j
> ----------------------------------------------------------------
>                 Key: AMQ-4008
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.6.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 5.7.0
> SEVERE: The web application [/camel-example-activemq-tomcat] created a ThreadLocal with
key of type [org.apache.log4j.helpers.ThreadLocalMap] (value [org.apache.log4j.helpers.ThreadLocalMap@1eb0cd0])
and a value of type [java.util.Hashtable] (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.
> I got a bit annoyed by this when I was working on a new example for Apache Camel with
an embedded AMQ broker. So I am digging into fixing this. Its in the start() method.

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:

View raw message