[QPID-6558] Queue can continue to grow after connection closes and does not appear in qpid-stat

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Cannot Reproduce
• Affects Version/s: 0.18
• Component/s: Broker-J
• Labels: memory_leak

Environment

RHEL Server 6.4, 64-bit
Java SE 1.7.0_51 x86_64

• Assignee: Unassigned
• Reporter: David Friedman
• Created: 28/May/15 17:56
• Updated: 18/Jun/15 14:17
• Resolved: 18/Jun/15 14:17

Description

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.