[
https://issues.apache.org/jira/browse/QPID-6558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14591818#comment-14591818
]
Rob Godfrey commented on QPID-6558:
-----------------------------------
Hi David - apologies for not responding to this sooner.
Have you tried reproducing this issue on a recent release of the Java Broker
(0.32 for instance)? The logic for auto-deleting of queues and managing
connections has changed a lot in the last 2.5 years so any bug in 0.18 may no
longer be present.
> Queue can continue to grow after connection closes and does not appear in
> qpid-stat
> -----------------------------------------------------------------------------------
>
> Key: QPID-6558
> URL: https://issues.apache.org/jira/browse/QPID-6558
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.18
> Environment: RHEL Server 6.4, 64-bit
> Java SE 1.7.0_51 x86_64
> Reporter: David Friedman
> Labels: memory_leak
>
> A (Java JMS) client disconnected from the broker. (Probably killed with a
> SIGTERM.) It had a queue for a topic that apparently continued to grow after
> the connection was closed.
> We have a cron to periodically log all queues and other broker information
> using qpid-stat. The next log after the client shutdown does not show the
> queue. However, the queue was apparently still being maintained internally
> by the broker and had new messages appended to it. The broker eventually ran
> out of memory. We have the broker JVM set up to dump its heap when there is
> an OutOfMemoryError exception. Examining the heap dump showed most of the
> memory was being used by the queue from the client that had disconnected.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
