I am running 5.4.1. Some of my durable subscribers have trouble reconnecting to the topic if they have been unproperly shutdown. The error is:
INFO | jvm 1 | 2010/12/01 03:14:28 | WARN | Failed to add Connection INFO | jvm 1 | 2010/12/01 03:14:28 | javax.jms.InvalidClientIDException: Broker: TABMQCORE - Client: TAB.event.instrument_RM_99 already connected from /10.100.54.13:51996 INFO | jvm 1 | 2010/12/01 03:14:28 | at org.apache.activemq.broker.region.RegionBroker.addConnection(RegionBroker.java:242) INFO | jvm 1 | 2010/12/01 03:14:28 | at org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:85) INFO | jvm 1 | 2010/12/01 03:14:28 | at org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.java:78) INFO | jvm 1 | 2010/12/01 03:14:28 | at org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:85) INFO | jvm 1 | 2010/12/01 03:14:28 | at org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:85) INFO | jvm 1 | 2010/12/01 03:14:28 | at org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:91) INFO | jvm 1 | 2010/12/01 03:14:28 | at org.apache.activemq.broker.TransportConnection.processAddConnection(TransportConnection.java:694) INFO | jvm 1 | 2010/12/01 03:14:28 | at org.apache.activemq.broker.jmx.ManagedTransportConnection.processAddConnection(ManagedTransportConnection.java:83) INFO | jvm 1 | 2010/12/01 03:14:28 | at org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:137) INFO | jvm 1 | 2010/12/01 03:14:28 | at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:309) INFO | jvm 1 | 2010/12/01 03:14:28 | at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:185) INFO | jvm 1 | 2010/12/01 03:14:28 | at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:69) INFO | jvm 1 | 2010/12/01 03:14:28 | at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113) INFO | jvm 1 | 2010/12/01 03:14:28 | at org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:228) INFO | jvm 1 | 2010/12/01 03:14:28 | at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83) INFO | jvm 1 | 2010/12/01 03:14:28 | at org.apache.activemq.transport.nio.NIOTransport.serviceRead(NIOTransport.java:129) INFO | jvm 1 | 2010/12/01 03:14:28 | at org.apache.activemq.transport.nio.NIOTransport.access$000(NIOTransport.java:44) INFO | jvm 1 | 2010/12/01 03:14:28 | at org.apache.activemq.transport.nio.NIOTransport$1.onSelect(NIOTransport.java:68) INFO | jvm 1 | 2010/12/01 03:14:28 | at org.apache.activemq.transport.nio.SelectorSelection.onSelect(SelectorSelection.java:94) INFO | jvm 1 | 2010/12/01 03:14:28 | at org.apache.activemq.transport.nio.SelectorWorker$1.run(SelectorWorker.java:119) INFO | jvm 1 | 2010/12/01 03:14:28 | at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) INFO | jvm 1 | 2010/12/01 03:14:28 | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) INFO | jvm 1 | 2010/12/01 03:14:28 | at java.lang.Thread.run(Thread.java:636) I am unable to remove the false connection through JConsole and the only way to reconnect the subscriber is to change the ClientID, which of course loses all of the pending messages if there are any. Has anyone else experienced this issue? The application connecting is C# using openwire. -- View this message in context: http://activemq.2283324.n4.nabble.com/Durable-Subscriber-reconnect-issue-tp3067684p3067684.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
