David Friedman created QPID-6558:
------------------------------------
Summary: 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
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]
