[
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:01 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 ...->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.
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
