[ https://issues.apache.org/jira/browse/ARTEMIS-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Bertram reassigned ARTEMIS-741: -------------------------------------- Assignee: Justin Bertram > memory leak when using STOMP protocol > ------------------------------------- > > Key: ARTEMIS-741 > URL: https://issues.apache.org/jira/browse/ARTEMIS-741 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker, Stomp > Affects Versions: 1.4.0 > Environment: JDK 8, Apache Tomcat server or standalone app, Linux or > Windows > Reporter: Mitchell Ackerman > Assignee: Justin Bertram > > 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 > -- This message was sent by Atlassian JIRA (v6.3.4#6332)