[QPID-6951] [Java Client] AMQSession.deregisterConsumer() leaks Memory

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.18, 0.22, 0.32, qpid-java-6.0
• Fix Version/s: qpid-java-6.0.1, qpid-java-6.1
• Component/s: JMS AMQP 0-x
• Assignee: Keith Wall
• Reporter: Lorenz Quack
• Created: 15/Dec/15 10:12
• Updated: 02/Oct/19 19:22
• Resolved: 08/Jan/16 13:27

Description

If a JMS user continually closes consumers on the same transactional session, a memory leak occurs at the following location. The leak remains until the Session is closed (Session#close()) or the session is rolled-back. (Session#rollback()).

AMQSession.deregisterConsumer() contains the following code:

if (_transacted)
{
    _removedConsumers.add(consumer);
}

However, the _removedConsumers list is only cleaned up on rollback and nowhere else.

This leak appears to be longstanding. It looks like it was added at M3 (QPID-832).