activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philippe Mouawad (Created) (JIRA)" <>
Subject [jira] [Created] (AMQ-3529) Calling Thread.interrupt while in MessageConsumer#receive(timeout) generates and leaks Connection
Date Sat, 08 Oct 2011 16:04:29 GMT
Calling Thread.interrupt while in MessageConsumer#receive(timeout) generates
and leaks Connection 

                 Key: AMQ-3529
             Project: ActiveMQ
          Issue Type: Bug
          Components: JMS client
    Affects Versions: 5.5.0
            Reporter: Philippe Mouawad

While running tests with JMeter and calling stop while test is running, I see that Transport
thread stays open and all close() on Connection, MessageConsumer, Session calls fails with
2011/10/08 17:16:59 ERROR - jmeter.protocol.jms.client.ReceiveSubscriber: Error during close:
	at org.apache.activemq.util.JMSExceptionSupport.create(
	at org.apache.activemq.ActiveMQConnection.doSyncSendPacket(
	at org.apache.activemq.ActiveMQConnection.close(
	at org.apache.jmeter.protocol.jms.Utils.close(
	at org.apache.jmeter.protocol.jms.client.ReceiveSubscriber.close(
	at org.apache.jmeter.protocol.jms.sampler.SubscriberSampler.threadFinished(
	at org.apache.jmeter.threads.JMeterThread$ThreadListenerTraverser.addNode(
	at org.apache.jorphan.collections.HashTree.traverseInto(
	at org.apache.jorphan.collections.HashTree.traverse(
	at org.apache.jmeter.threads.JMeterThread.threadFinished(
Caused by:
	at org.apache.activemq.transport.WireFormatNegotiator.oneway(
	at org.apache.activemq.transport.MutexTransport.oneway(
	at org.apache.activemq.transport.ResponseCorrelator.asyncRequest(
	at org.apache.activemq.transport.ResponseCorrelator.request(
	at org.apache.activemq.ActiveMQConnection.doSyncSendPacket(
	... 10 more

I opened an issue in JMeter with all details but I think issue is in ActiveMQ, see:

Issue contains a Test Plan, and all details.


This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message