Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F32439CC8 for ; Wed, 18 Jul 2012 20:03:35 +0000 (UTC) Received: (qmail 67042 invoked by uid 500); 18 Jul 2012 20:03:35 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 66967 invoked by uid 500); 18 Jul 2012 20:03:34 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 66959 invoked by uid 99); 18 Jul 2012 20:03:34 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jul 2012 20:03:34 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 9AD0D14281C for ; Wed, 18 Jul 2012 20:03:34 +0000 (UTC) Date: Wed, 18 Jul 2012 20:03:34 +0000 (UTC) From: "Michael Pilone (JIRA)" To: dev@activemq.apache.org Message-ID: <437867842.71383.1342641814636.JavaMail.jiratomcat@issues-vm> In-Reply-To: <825186208.69653.1342628614673.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Comment Edited] (AMQ-3938) Memory Leak w/Temporary Queues and JMX MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMQ-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13417627#comment-13417627 ] Michael Pilone edited comment on AMQ-3938 at 7/18/12 8:02 PM: -------------------------------------------------------------- Looking at the JMX info via JConsole, I can see that under org.apache.activemq->Broker Name->Producer->TempQueue there are hundreds or thousands of entries. Way more than what is under org.apache.activemq->Broker Name->TempQueue which contains about 45 entries. This is after running the broker for 8 days, about half of the expected life before exhausting memory. What puts entries under Producer and does it ever clean them up? was (Author: mpilone): Looking at the JMX info via JConsole, I can see that under org.apache.activemq->Broker Name->Producer->TempQueue there are hundreds or thousands of entries. Way more than what is under ...->Broker Name->TempQueue which contains about 45 entries. This is after running the broker for 8 days, about half of the expected life before exhausting memory. What puts entries under Producer and does it ever clean them up? > Memory Leak w/Temporary Queues and JMX > -------------------------------------- > > Key: AMQ-3938 > URL: https://issues.apache.org/jira/browse/AMQ-3938 > Project: ActiveMQ > Issue Type: Bug > Components: Broker, JMX > Affects Versions: 5.6.0 > Environment: Java 6 > ActiveMQ 5.6.0 > Apache Camel 2.10.0 > Network of brokers (2 nodes) > Solaris > Reporter: Michael Pilone > Attachments: Eclipse Memory Analyzer_2012-07-18_11-46-58.png > > > I'm seeing a slow memory leak in our broker process which appears to be related to temporary queues and JMX. We had major memory leak problems before, but the 5.6.0 release fixed the majority of them. This leak seems to take about 2 weeks to fill 512MB heap but ultimately it will bring down the JVM. > > The process which eventually runs out of memory simply runs an embeded broker which other clients connected to it via TCP. There are a couple static Camel routes, but nothing major in this process. Other clients (connected via TCP) make heavy use of pooled connections, Apache Camel, and temporary queues for request/reply messaging. > > I'm still looking into the issue but I've attached a MAT memory analysis to see if anyone else has seen a related problem. It looks like the temporary queues are getting registered in JMX and never removed but I'm just guessing right now. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira