[jira] [Created] (ARTEMIS-2553) On connection failure, not receiving JMS ExceptionListener message
Mitchell Ackerman created ARTEMIS-2553:
--
Summary: On connection failure, not receiving JMS
ExceptionListener message
Key: ARTEMIS-2553
URL: https://issues.apache.org/jira/browse/ARTEMIS-2553
Project: ActiveMQ Artemis
Issue Type: Bug
Components: ActiveMQ-Artemis-Native
Affects Versions: 1.6.0
Environment: Amazon linux on Tomcat 9.0, JDK 1.8
Reporter: Mitchell Ackerman
Assignee: Clebert Suconic
On a connection failure, artemis detects the failure:
2019-11-14 05:00:58,970 [Thread-13691
(ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$3@23e9e1b6)]
WARN [RemotingConnectionImpl.fail() 198] - AMQ212037: Connection failure has
been detected: AMQ119014: Did not receive data from /10.94.80.72:37708 within
the 60,000ms connection TTL. The connection will now be closed.
[code=CONNECTION_TIMEDOUT]
we have a JMS Exception listener added:
connection.setExceptionListener(new ExceptionListener()
\{connection.setExceptionListener(new ExceptionListener() { @Override public
void onException(JMSException exception) {
log.info(LogFactory.getJsonLogger("connection has failed, message: " +
exception.getMessage())); consumer.accept(exception); } });
but never receive any event
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARTEMIS-741) memory leak when using STOMP protocol
[ https://issues.apache.org/jira/browse/ARTEMIS-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15531127#comment-15531127 ] Mitchell Ackerman commented on ARTEMIS-741: --- Thanks for the fast turnaround guys, super support. > 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 > Fix For: 1.5.0 > > Attachments: dump-10.89.1.31.pcap > > > 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)
[jira] [Commented] (ARTEMIS-741) memory leak when using STOMP protocol
[ https://issues.apache.org/jira/browse/ARTEMIS-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15514647#comment-15514647 ] Mitchell Ackerman commented on ARTEMIS-741: --- BTW, this pcap is from a capture between our STOMP 1.1 client and the server running HornetQ. We don't yet have our client talking to ArtemisMQ, but i've been using a test STOMP 1.0 client to test the ArtemisMQ server. I can see if I can get a pcap for the 1.1 client if you like. > 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 > Attachments: dump-10.89.1.31.pcap > > > 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)
[jira] [Updated] (ARTEMIS-741) memory leak when using STOMP protocol
[ https://issues.apache.org/jira/browse/ARTEMIS-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mitchell Ackerman updated ARTEMIS-741: -- Attachment: dump-10.89.1.31.pcap See packet 39 for an example of a subscription with an ID > 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 > Attachments: dump-10.89.1.31.pcap > > > 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)
[jira] [Commented] (ARTEMIS-741) memory leak when using STOMP protocol
[ https://issues.apache.org/jira/browse/ARTEMIS-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15514573#comment-15514573 ] Mitchell Ackerman commented on ARTEMIS-741: --- 1.1, but it occurs with 1.0 also > 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)
[jira] [Updated] (ARTEMIS-741) memory leak when using STOMP protocol
[ https://issues.apache.org/jira/browse/ARTEMIS-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mitchell Ackerman updated ARTEMIS-741: -- Component/s: Broker > 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 > > 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)
[jira] [Created] (ARTEMIS-741) memory leak when using STOMP protocol
Mitchell Ackerman created ARTEMIS-741: - Summary: 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: Stomp Affects Versions: 1.4.0 Environment: JDK 8, Apache Tomcat server or standalone app, Linux or Windows Reporter: Mitchell Ackerman 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)
