[
https://issues.apache.org/jira/browse/AMQ-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789476#comment-13789476
]
Graham Leggett commented on AMQ-4789:
-------------------------------------
5.9-SNAPSHOT can only be used with difficulty in our case.
We tried to switch the backend database from kahaDB to levelDB (as kahaDB
appeared as one of the objects that was leaking the above objects) but no
difference.
We cannot keep v5.8.0 up and running for more than a few hours at a time, and
each time activemq hits the wall it loses all trace of messages processed,
leaving us at an earlier state being forced to process messages again from
scratch. Activemq is fatally broken in its current form.
> 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)
