[ARTEMIS-741] memory leak when using STOMP protocol

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.4.0
• Fix Version/s: 1.5.0
• Component/s: Broker, STOMP

Environment

JDK 8, Apache Tomcat server or standalone app, Linux or Windows

• Assignee: Justin Bertram
• Reporter: Mitchell Ackerman
• Created: 20/Sep/16 20:44
• Updated: 21/Oct/16 18:42
• Resolved: 27/Sep/16 00:44

Description

ArtemisMQ exhibits a memory leak when using the STOMP protocol.

Steps to reproduce:

1. Configure a server with a JMS topic, my example uses an EmbeddedJMS server
2. Connect to the server using the STOMP protocol
3. Subscribe to the topic with a selector
4. publish some messages to the topic that match the selector (this step may not be necessary)
5. Unsubscribe from the topic
6. publish some messages to the topic that match the selector

The messages published after the unsubscribe are retained in a QueueImpl object, messageReferences queue and are never cleaned up unless the client disconnects. The QueueImpl object has 0 Consumers (ConsumerList size is 0), and the QueueImpl object retains the filter from the subscription.

See also http://activemq.2283324.n4.nabble.com/potential-memory-leak-when-using-STOMP-protocol-td4716643.html

Issue Links

• links to: GitHub Pull Request #801