Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Fri, 7 Sep 2012 04:59:12 +1100 (NCT)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <814534376.45582.1346954352464.JavaMail.jiratomcat@arcas>
In-Reply-To: <1386703315.13223.1344070863764.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Updated] (AMQ-3962) Memory leak bacause of
 InactivityMonitor thread
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Claus Ibsen updated AMQ-3962:
-----------------------------

    Fix Version/s: 5.7.0
    
> Memory leak bacause of InactivityMonitor thread
> -----------------------------------------------
>
>                 Key: AMQ-3962
>                 URL: https://issues.apache.org/jira/browse/AMQ-3962
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMS client
>    Affects Versions: 5.5.0, 5.6.0
>         Environment: Ubuntu 12.04 x64
> Tomcat 7.0.28
> Oracle JDK 1.6.0_32
>            Reporter: Sergey
>            Assignee: Claus Ibsen
>             Fix For: 5.7.0
>
>         Attachments: memory_leak_inactivity_monitor.png, patch.txt
>
>
> When I re-start my web application which connects to a standalone ActiveMQ broker via Tomcat Manager, I got OutOfMemoryError in PermGenSpace. The profiler shows that after stopping the web application it could not be unloaded from memory because of a memory leak caused by InactivityMonitor thread, see the screenshot for detail. 

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