You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by ksu <ks...@yahoo.com> on 2007/07/16 20:48:38 UTC
Problem with Networked Brokers
Using the 5.0 Snapshot, I am getting the following exceptions in the brokers:
Setup:
- Start three brokers using multi-cast as the discovery protocol with
names of: sender, receiver, receiver2.
The XML configuration used is similar to the one found in
activemq-core/src/test/resources/org/apache/activemq/usecases/multicast-broker-1.xml
Steps:
- Kill one receiver2 and restart, one or both sender and receiver now
gets into an infinite loop
with the the excpetion:
nboundreceiver already connected
javax.jms.InvalidClientIDException: Broker: receiver - Client:
NC_receiverToo_inboundreceiver already connected
at
org.apache.activemq.broker.region.RegionBroker.addConnection(RegionBroker.java:210)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:83)
at
org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.java:71)
at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:83)
at
org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:93)
at
org.apache.activemq.broker.TransportConnection.processAddConnection(TransportConnection.java:685)
at
org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:121)
at
org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:283)
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:188)
at
org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:96)
at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65)
at
org.apache.activemq.transport.vm.VMTransport.iterate(VMTransport.java:224)
at
org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:97)
at
org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:39)
The only fix is to restart all brokers.
Is this a known bug or a configuration issue?
--
View this message in context: http://www.nabble.com/Problem-with-Networked-Brokers-tf4090473s2354.html#a11628738
Sent from the ActiveMQ - User mailing list archive at Nabble.com.