We are using activeMQ 5.7 release and use static network of brokers. Every now and then( 12 hrs or so) we get javax.jms.InvalidClientIDException: Broker: broker-1 - Client: network-broker-1_broker-3_outbound already connected from tcp://<ipaddr>:<port> at org.apache.activemq.broker.region.RegionBroker.addConnection(RegionBroker.java:223) at org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:85) at org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.java:79) at org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:85) at org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:85) at org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:85) at org..AuthenticationBroker.addConnection(AuthenticationBroker.java:121) at org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:91) at org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:91) at org.apache.activemq.broker.TransportConnection.processAddConnection(TransportConnection.java:712) at org.apache.activemq.broker.jmx.ManagedTransportConnection.processAddConnection(ManagedTransportConnection.java:80) at org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:139) at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:294) at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:152) at org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50) at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113) at org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:256) at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83) at org.apache.activemq.transport.nio.NIOTransport.serviceRead(NIOTransport.java:138) at org.apache.activemq.transport.nio.NIOTransport$1.onSelect(NIOTransport.java:69) at org.apache.activemq.transport.nio.SelectorSelection.onSelect(SelectorSelection.java:94) at org.apache.activemq.transport.nio.SelectorWorker$1.run(SelectorWorker.java:119) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744)
It happens in the network with lot of load. There is only one consumer and multiple listeners on the network. Did some research and found http://activemq.2283324.n4.nabble.com/Identifying-disconnected-client-id-in-a-network-of-brokers-td4653652.html that by removing the clientID before it is added again might help. But to no avail. Any ideas what causes it and possible solutions? -- View this message in context: http://activemq.2283324.n4.nabble.com/javax-jms-InvalidClientIDException-Broker-broker-1-Client-network-broker-1-broker-3-outbound-already-tp4678440.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.