You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Graham Leggett (JIRA)" <ji...@apache.org> on 2013/10/07 17:28:42 UTC
[jira] [Updated] (AMQ-4789) Slow leak:
org.apache.activemq.broker.jmx.ManagedTransportConnection
[ https://issues.apache.org/jira/browse/AMQ-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Graham Leggett updated AMQ-4789:
--------------------------------
Attachment: activemq-leak.tiff
activemq-leak-detail.tiff
Screenshots from Eclipse MAT showing leaked objects.
> Slow leak: org.apache.activemq.broker.jmx.ManagedTransportConnection
> --------------------------------------------------------------------
>
> Key: AMQ-4789
> URL: https://issues.apache.org/jira/browse/AMQ-4789
> Project: ActiveMQ
> Issue Type: Bug
> Components: JMX
> Affects Versions: 5.8.0
> Environment: INFO | jvm 1 | 2013/10/07 10:17:29 | Java Runtime: Sun Microsystems Inc. 1.6.0_24 /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre
> INFO | jvm 1 | 2013/10/07 10:17:29 | Heap sizes: current=83008k free=78872k max=4190080k
> Reporter: Graham Leggett
> Labels: leak
> Attachments: activemq-leak-detail.tiff, activemq-leak.tiff
>
>
> When activemq is configured with an amqp transport and SSL, and where clients make short lived polled connections to the queue, a slow leak exists that kills the server within about 12 hours or so (for us) with the following:
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> Obtaining a heap dump in this state reveals that about 3/4 of our heap is used by the org.apache.activemq.broker.jmx.ManagedTransportConnection as per the attached screenshots.
--
This message was sent by Atlassian JIRA
(v6.1#6144)