[jira] Commented: (AMQ-1121) Kaha DB hangs on restart
[ https://issues.apache.org/activemq/browse/AMQ-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37823 ] Rob Davies commented on AMQ-1121: - could you provide a test case ? Kaha DB hangs on restart Key: AMQ-1121 URL: https://issues.apache.org/activemq/browse/AMQ-1121 Project: ActiveMQ Issue Type: Bug Components: Message Store Affects Versions: 4.1.0 Environment: Windows XP, NetApp Reporter: Vadim Pesochinskiy Assigned To: Rob Davies Priority: Blocker Fix For: 4.1.0 I run a bunch or messages through AMQ, then restarted AMQ and it hangs. Following are the last messages that I see. AMQ is not listening on the configured port. 2007-01-06 01:35:29,723 [main ] DEBUG DataManager - End of data file reached at (header was invalid): offset = 810, file = 1, size = 219 2007-01-06 01:35:29,754 [JMX connector ] INFO ManagementContext - JMX consoles can connect to service:jmx:rmi:///jndi/rmi://localhost:11099/jmxrmi 2007-01-06 01:35:32,660 [main ] DEBUG DataManager - End of data file reached at (header was invalid): offset = 88244949, file = 5, size = 100856 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (AMQ-1121) Kaha DB hangs on restart
[ https://issues.apache.org/activemq/browse/AMQ-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies reassigned AMQ-1121: --- Assignee: Rob Davies Kaha DB hangs on restart Key: AMQ-1121 URL: https://issues.apache.org/activemq/browse/AMQ-1121 Project: ActiveMQ Issue Type: Bug Components: Message Store Affects Versions: 4.1.0 Environment: Windows XP, NetApp Reporter: Vadim Pesochinskiy Assigned To: Rob Davies Priority: Blocker Fix For: 4.1.0 I run a bunch or messages through AMQ, then restarted AMQ and it hangs. Following are the last messages that I see. AMQ is not listening on the configured port. 2007-01-06 01:35:29,723 [main ] DEBUG DataManager - End of data file reached at (header was invalid): offset = 810, file = 1, size = 219 2007-01-06 01:35:29,754 [JMX connector ] INFO ManagementContext - JMX consoles can connect to service:jmx:rmi:///jndi/rmi://localhost:11099/jmxrmi 2007-01-06 01:35:32,660 [main ] DEBUG DataManager - End of data file reached at (header was invalid): offset = 88244949, file = 5, size = 100856 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (AMQ-1117) It would be helpful if some of the log messages that are logged at higher severity levels than they are presently
[ https://issues.apache.org/activemq/browse/AMQ-1117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies reassigned AMQ-1117: --- Assignee: Rob Davies It would be helpful if some of the log messages that are logged at higher severity levels than they are presently - Key: AMQ-1117 URL: https://issues.apache.org/activemq/browse/AMQ-1117 Project: ActiveMQ Issue Type: Wish Affects Versions: 4.0, 4.0.1, 4.0.2, 4.1.0 Reporter: Chris Hofstaedter Assigned To: Rob Davies It would be helpful if the messages pertaining to transport interrupted and transport resumed were logged at INFO rather than DEBUG. It would be helpful if the messages pertaining to security errors were logged at ERROR rather than INFO. All of these log messages are in DemandForwardingBridgeSupport in the following functions: public void start() // for Transport Interrupted public void start() // for Transport Resumed protected void serviceRemoteException() // for Security errors -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-1117) It would be helpful if some of the log messages that are logged at higher severity levels than they are presently
[ https://issues.apache.org/activemq/browse/AMQ-1117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies resolved AMQ-1117. - Resolution: Fixed Fix Version/s: 4.2.0 resolved SVN revision 493696 It would be helpful if some of the log messages that are logged at higher severity levels than they are presently - Key: AMQ-1117 URL: https://issues.apache.org/activemq/browse/AMQ-1117 Project: ActiveMQ Issue Type: Wish Affects Versions: 4.0, 4.0.1, 4.0.2, 4.1.0 Reporter: Chris Hofstaedter Assigned To: Rob Davies Fix For: 4.2.0 It would be helpful if the messages pertaining to transport interrupted and transport resumed were logged at INFO rather than DEBUG. It would be helpful if the messages pertaining to security errors were logged at ERROR rather than INFO. All of these log messages are in DemandForwardingBridgeSupport in the following functions: public void start() // for Transport Interrupted public void start() // for Transport Resumed protected void serviceRemoteException() // for Security errors -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (AMQ-1005) Network of brokers duplicates events
[ https://issues.apache.org/activemq/browse/AMQ-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies reassigned AMQ-1005: --- Assignee: Rob Davies Network of brokers duplicates events Key: AMQ-1005 URL: https://issues.apache.org/activemq/browse/AMQ-1005 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 4.0.1, 4.0.2 Reporter: Linda Floren Assigned To: Rob Davies Priority: Blocker Attachments: ConduitSubscriptionTest.java, SimpleMessageListener.java I've created a test scenario to reproduce the error: Two brokers A and B run with networkconnectors towards each other with conduitSubscriptions=false. The publisher is connected to broker A. There are n Subscribers with identical filters on each broker. Result: The subscribers on broker B receive each event n times. (The subscribers on broker A work fine). It appears as if the subscriptions are treated as conduit subscriptions in the dispatching process on broker B. I've attached my test. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQCPP-38) Async error on broker when running integration tests
[ https://issues.apache.org/activemq/browse/AMQCPP-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler updated AMQCPP-38: - Fix Version/s: 1.1 Async error on broker when running integration tests Key: AMQCPP-38 URL: https://issues.apache.org/activemq/browse/AMQCPP-38 Project: ActiveMQ C++ Client Issue Type: Bug Affects Versions: 1.1 Reporter: Albert Strasheim Assigned To: Nathan Mittler Fix For: 1.1 Brought over from the comments in AMQCPP-28. Sometimes when running the integration tests against the AMQ broker from trunk, ones sees the following message from the broker: ERROR Service - Async error occurred: java.lang.IllegalStateException: Cannot remove a consumer that had not been registered: ID:xxx-36153-1166305227288-5:16:-1:1 at org.apache.activemq.broker.TransportConnection.processRemoveConsumer(TransportConnection.java:593) at org.apache.activemq.command.RemoveInfo.visit(RemoveInfo.java:64) at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:287) at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:178) at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65) at org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122) at org.apache.activemq.transport.stomp.StompTransportFilter.sendToActiveMQ(StompTransportFilter.java:74) at org.apache.activemq.transport.stomp.ProtocolConverter.sendToActiveMQ(ProtocolConverter.java:119) at org.apache.activemq.transport.stomp.ProtocolConverter.onStompUnsubscribe(ProtocolConverter.java:379) at org.apache.activemq.transport.stomp.ProtocolConverter.onStompCommad(ProtocolConverter.java:151) at org.apache.activemq.transport.stomp.StompTransportFilter.onCommand(StompTransportFilter.java:64) at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84) at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:137) at java.lang.Thread.run(Thread.java:595) Using the default activemq.xml, I can reproduce the IllegalStateException quite reliabily: 1. Start a fresh copy of the broker (4.2 from yesterday's trunk) 2. Run the integration test under Valgrind 3. IllegalStateException happens at the end of integration::durable::DurableTester::test or at the start of integration::expiration::ExpirationTest::testExpired. Subsequent test runs don't yield the error, until the broker is restarted. I don't know if this issue could be time-dependent - if it is, it could explain why I only see it when running under Valgrind. On Linux, I also just got the following test failure for the first time (not running under Valgrind): 1) test: integration::durable::DurableTester::test (E) uncaught exception of unknown type -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQCPP-32) Stomp messages don't preserve property types: please document this behaviour
[ https://issues.apache.org/activemq/browse/AMQCPP-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler updated AMQCPP-32: - Fix Version/s: 1.1 Stomp messages don't preserve property types: please document this behaviour Key: AMQCPP-32 URL: https://issues.apache.org/activemq/browse/AMQCPP-32 Project: ActiveMQ C++ Client Issue Type: Wish Components: Stomp Affects Versions: 1.1 Reporter: Albert Strasheim Assigned To: Nathan Mittler Priority: Trivial Fix For: 1.1 I am producing messages from Java and C++ using ActiveMQ and AMQCPP, respectively. Messages I produce have an int property set on them which I want to select on, again in Java or C++. As far as I can tell from the [Stomp Protocol specification|http://stomp.codehaus.org/Protocol] there is no way to specify the types of message headers. As a result, all the messages end up with String properties as can be be seen in the unmarshal method of [org.apache.activemq.transport.stomp|http://svn.apache.org/viewvc/incubator/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/transport/stomp/StompWireFormat.java?revision=470398view=markup]. I can work around this problem by selecting on id=123||id='123' in both Java and C++, but it seems a bit suboptimal. At least, this issue should be documented somewhere in activemq::connector::stomp::commands::StompMessage to help other people who can't figure out why their selectors don't work. We could consider adding a function that allows the user to specify that Stomp message properties should be sent in a type safe manner, and then prepend some kind of string to the property name to indicate the type. StompWireFormat on the Java side could check for this case and set the typed properties accordingly. This is probably too much of a hack -- people who want typed properties to work right can use Openwire in the (hopefully) near future. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (AMQCPP-27) Issues reported by Valgrind when running unit tests
[ https://issues.apache.org/activemq/browse/AMQCPP-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler closed AMQCPP-27. Resolution: Fixed If the leaks shown by valgrind end up being real leaks or if more leaks pop up - we'll just open a new issue. Issues reported by Valgrind when running unit tests --- Key: AMQCPP-27 URL: https://issues.apache.org/activemq/browse/AMQCPP-27 Project: ActiveMQ C++ Client Issue Type: Bug Affects Versions: 1.1 Reporter: Albert Strasheim Assigned To: Nathan Mittler Fix For: 1.1 Attachments: activemq-cpp-deletes.diff, activemq-cpp-valgrind.log Valgrind 3.2.1 reported a few issues when running the ActiveMQ C++ unit tests. Some of them were simple cases of mismatched new[] and delete[] (patch attached). Valgrind also reports a few memory leaks, some probably the same as found by Rational Purify. Complete Valgrind log attached (after I fixed the deletes). I ran Valgrind as follows: valgrind \ --tool=memcheck \ --leak-check=yes \ --error-limit=no \ --num-callers=20 \ --freelist-vol=536870912 \ -v \ ./activemq-test -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQCPP-38) Async error on broker when running integration tests
[ https://issues.apache.org/activemq/browse/AMQCPP-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37827 ] Nathan Mittler commented on AMQCPP-38: -- Running the integration tests several times in a row against the latest trunk of the broker (everything co-located on the same OS X machine), I do not get this error. Could you please provide your environment? Also, try running against the broker's latest trunk and see if you still have problems. Async error on broker when running integration tests Key: AMQCPP-38 URL: https://issues.apache.org/activemq/browse/AMQCPP-38 Project: ActiveMQ C++ Client Issue Type: Bug Affects Versions: 1.1 Reporter: Albert Strasheim Assigned To: Nathan Mittler Fix For: 1.1 Brought over from the comments in AMQCPP-28. Sometimes when running the integration tests against the AMQ broker from trunk, ones sees the following message from the broker: ERROR Service - Async error occurred: java.lang.IllegalStateException: Cannot remove a consumer that had not been registered: ID:xxx-36153-1166305227288-5:16:-1:1 at org.apache.activemq.broker.TransportConnection.processRemoveConsumer(TransportConnection.java:593) at org.apache.activemq.command.RemoveInfo.visit(RemoveInfo.java:64) at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:287) at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:178) at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65) at org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122) at org.apache.activemq.transport.stomp.StompTransportFilter.sendToActiveMQ(StompTransportFilter.java:74) at org.apache.activemq.transport.stomp.ProtocolConverter.sendToActiveMQ(ProtocolConverter.java:119) at org.apache.activemq.transport.stomp.ProtocolConverter.onStompUnsubscribe(ProtocolConverter.java:379) at org.apache.activemq.transport.stomp.ProtocolConverter.onStompCommad(ProtocolConverter.java:151) at org.apache.activemq.transport.stomp.StompTransportFilter.onCommand(StompTransportFilter.java:64) at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84) at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:137) at java.lang.Thread.run(Thread.java:595) Using the default activemq.xml, I can reproduce the IllegalStateException quite reliabily: 1. Start a fresh copy of the broker (4.2 from yesterday's trunk) 2. Run the integration test under Valgrind 3. IllegalStateException happens at the end of integration::durable::DurableTester::test or at the start of integration::expiration::ExpirationTest::testExpired. Subsequent test runs don't yield the error, until the broker is restarted. I don't know if this issue could be time-dependent - if it is, it could explain why I only see it when running under Valgrind. On Linux, I also just got the following test failure for the first time (not running under Valgrind): 1) test: integration::durable::DurableTester::test (E) uncaught exception of unknown type -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQCPP-38) Async error on broker when running integration tests
[
https://issues.apache.org/activemq/browse/AMQCPP-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37829
]
Albert Strasheim commented on AMQCPP-38:
I've been running the integration tests repeatedly on Windows.
DurableTester fails most of the time. Also seeing exceptions in the broker in
new places. Also got this crash, which is quite interesting:
{noformat}
1) test: inR6025
- pure virtual function call
tegration::durable::DurableTester::test (E)
uncaught exception of unknown type
2) test: integration::simple::SimpleTester::test (E)
uncaught exception of unknown type
{noformat}
Async error on broker when running integration tests
Key: AMQCPP-38
URL: https://issues.apache.org/activemq/browse/AMQCPP-38
Project: ActiveMQ C++ Client
Issue Type: Bug
Affects Versions: 1.1
Reporter: Albert Strasheim
Assigned To: Nathan Mittler
Fix For: 1.1
Brought over from the comments in AMQCPP-28.
Sometimes when running the integration tests against the AMQ broker from
trunk, ones sees the following message from the broker:
ERROR Service - Async error occurred:
java.lang.IllegalStateException: Cannot remove a consumer that had not been
registered: ID:xxx-36153-1166305227288-5:16:-1:1
at
org.apache.activemq.broker.TransportConnection.processRemoveConsumer(TransportConnection.java:593)
at org.apache.activemq.command.RemoveInfo.visit(RemoveInfo.java:64)
at
org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:287)
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:178)
at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65)
at
org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
at
org.apache.activemq.transport.stomp.StompTransportFilter.sendToActiveMQ(StompTransportFilter.java:74)
at
org.apache.activemq.transport.stomp.ProtocolConverter.sendToActiveMQ(ProtocolConverter.java:119)
at
org.apache.activemq.transport.stomp.ProtocolConverter.onStompUnsubscribe(ProtocolConverter.java:379)
at
org.apache.activemq.transport.stomp.ProtocolConverter.onStompCommad(ProtocolConverter.java:151)
at
org.apache.activemq.transport.stomp.StompTransportFilter.onCommand(StompTransportFilter.java:64)
at
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:137)
at java.lang.Thread.run(Thread.java:595)
Using the default activemq.xml, I can reproduce the IllegalStateException
quite reliabily:
1. Start a fresh copy of the broker (4.2 from yesterday's trunk)
2. Run the integration test under Valgrind
3. IllegalStateException happens at the end of
integration::durable::DurableTester::test or at the start of
integration::expiration::ExpirationTest::testExpired.
Subsequent test runs don't yield the error, until the broker is restarted. I
don't know if this issue could be time-dependent - if it is, it could explain
why I only see it when running under Valgrind.
On Linux, I also just got the following test failure for the first time (not
running under Valgrind):
1) test: integration::durable::DurableTester::test (E)
uncaught exception of unknown type
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQCPP-38) Async error on broker when running integration tests
[
https://issues.apache.org/activemq/browse/AMQCPP-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37830
]
Albert Strasheim commented on AMQCPP-38:
Here's the stacktrace on the broker that turns up when running the integration
tests repeatedly with both the broker and the integration tests running on
Windows XP SP2 with Sun Java 1.5.0_10 on a Core 2 Duo:
{noformat}
java.lang.IllegalArgumentException: The subscription does not exist:
ID:xxx-4402-1168189818390-5:210:-1:1
at
org.apache.activemq.broker.region.AbstractRegion.acknowledge(AbstractRegion.java:311)
at
org.apache.activemq.broker.region.RegionBroker.acknowledge(RegionBroker.java:401)
at
org.apache.activemq.broker.TransactionBroker.acknowledge(TransactionBroker.java:181)
at
org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:74)
at
org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:74)
at
org.apache.activemq.broker.MutableBrokerFilter.acknowledge(MutableBrokerFilter.java:88)
at
org.apache.activemq.broker.TransportConnection.processMessageAck(TransportConnection.java:456)
at org.apache.activemq.command.MessageAck.visit(MessageAck.java:179)
at
org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:258)
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:164)
at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65)
at
org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
at
org.apache.activemq.transport.stomp.StompTransportFilter.sendToActiveMQ(StompTransportFilter.java:74)
at
org.apache.activemq.transport.stomp.StompSubscription.onMessageDispatch(StompSubscription.java:71)
at
org.apache.activemq.transport.stomp.ProtocolConverter.onActiveMQCommad(ProtocolConverter.java:479)
at
org.apache.activemq.transport.stomp.StompTransportFilter.oneway(StompTransportFilter.java:56)
at
org.apache.activemq.transport.InactivityMonitor.oneway(InactivityMonitor.java:141)
at
org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:47)
at
org.apache.activemq.broker.TransportConnection.dispatch(TransportConnection.java:972)
at
org.apache.activemq.broker.TransportConnection.processDispatch(TransportConnection.java:709)
at
org.apache.activemq.broker.TransportConnection.iterate(TransportConnection.java:725)
at
org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:88)
at
org.apache.activemq.thread.DedicatedTaskRunner.access$000(DedicatedTaskRunner.java:25)
at
org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:39)
{noformat}
Async error on broker when running integration tests
Key: AMQCPP-38
URL: https://issues.apache.org/activemq/browse/AMQCPP-38
Project: ActiveMQ C++ Client
Issue Type: Bug
Affects Versions: 1.1
Reporter: Albert Strasheim
Assigned To: Nathan Mittler
Fix For: 1.1
Brought over from the comments in AMQCPP-28.
Sometimes when running the integration tests against the AMQ broker from
trunk, ones sees the following message from the broker:
ERROR Service - Async error occurred:
java.lang.IllegalStateException: Cannot remove a consumer that had not been
registered: ID:xxx-36153-1166305227288-5:16:-1:1
at
org.apache.activemq.broker.TransportConnection.processRemoveConsumer(TransportConnection.java:593)
at org.apache.activemq.command.RemoveInfo.visit(RemoveInfo.java:64)
at
org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:287)
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:178)
at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65)
at
org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
at
org.apache.activemq.transport.stomp.StompTransportFilter.sendToActiveMQ(StompTransportFilter.java:74)
at
org.apache.activemq.transport.stomp.ProtocolConverter.sendToActiveMQ(ProtocolConverter.java:119)
at
org.apache.activemq.transport.stomp.ProtocolConverter.onStompUnsubscribe(ProtocolConverter.java:379)
at
org.apache.activemq.transport.stomp.ProtocolConverter.onStompCommad(ProtocolConverter.java:151)
at
org.apache.activemq.transport.stomp.StompTransportFilter.onCommand(StompTransportFilter.java:64)
at
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:137)
at java.lang.Thread.run(Thread.java:595)
Using the default activemq.xml, I can reproduce
