You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2015/08/25 12:31:46 UTC

[jira] [Closed] (AMQ-5945) Tomcat 7.0.62 complains of memory leak when web app is stopped or reloaded

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

Robbie Gemmell closed AMQ-5945.
-------------------------------
    Resolution: Duplicate

Closing as dup of AMQ-5946 since that one has been updated and this one has not.

> Tomcat 7.0.62 complains of memory leak when web app is stopped or reloaded
> --------------------------------------------------------------------------
>
>                 Key: AMQ-5945
>                 URL: https://issues.apache.org/jira/browse/AMQ-5945
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMS client
>    Affects Versions: 5.10.2
>         Environment: Tomcat 7.0.62 , ActiveMQ 5.10.2 , Spring 4.1.2
>            Reporter: Nandini R
>
> We are using failover protocol to connect to broker. 
> Url is as :  "failover:("+brokerUrl+")?startupMaxReconnectAttempts=2&initialReconnectDelay=60000&maxReconnectAttempts=2
> Suppose I start web application with AMQ not running and then stop web application , I get below logs in tomcat
> SEVERE: The web application [/tcxoptimize] appears to have started a thread name
> d [ActiveMQ Connection Executor: unconnected] but has failed to stop it. This is
>  very likely to create a memory leak.
> Aug 25, 2015 11:27:59 AM org.apache.catalina.loader.WebappClassLoader clearRefer
> encesThreads
> SEVERE: The web application [/tcxoptimize] appears to have started a thread name
> d [ActiveMQ Task-1] but has failed to stop it. This is very likely to create a m
> emory leak.
> I can see these 2 threads in thread dump. 
> How do I close these on stopping web application ?
> On webapp shutdown I am shutting down message containers and closing spring context.
> I do not have issues if active MQ is running.
> 				



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)