[
https://issues.apache.org/jira/browse/AMQ-4008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445836#comment-13445836
]
Claus Ibsen commented on AMQ-4008:
----------------------------------
Thanks Gary
Yeah seems Claudio is on top of this.
There is another issue though with restarting an app in Tomcat, is that the JMX
connector seems to not close down properly, causing port to be use on reload.
2012-08-31 13:05:24,461 [JMX connector ] WARN ManagementContext
- Failed to start jmx connector: Cannot bind to URL
[rmi://localhost:1099/jmxrmi]: javax.naming.ServiceUnavailableException [Root
exception is java.rmi.ConnectException: Connection refused to host: localhost;
nested exception is:
java.net.ConnectException: Connection refused]
> Tomcat WARN on shutdown about ThreadLocal not cleared from log4j
> ----------------------------------------------------------------
>
> Key: AMQ-4008
> URL: https://issues.apache.org/jira/browse/AMQ-4008
> 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 [{activemq.broker=myBroker}]) 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: http://www.atlassian.com/software/jira
