So to get the best chance of getting help, I recommend you reproduce this in a unit test. Then we will be able to see exactly what's going on and give you the best answer. Networks of brokers can be tricky to get correct. I would advise you take a look at this test (which has 4 brokers like yours):
https://github.com/apache/activemq/blob/trunk/activemq-unit-tests/src/test/java/org/apache/activemq/usecases/RequestReplyToTopicViaThreeNetworkHopsTest.java And this test (which tests and verifies reconnect behavior): https://github.com/apache/activemq/blob/trunk/activemq-unit-tests/src/test/java/org/apache/activemq/network/NetworkReconnectTest.java On Mon, Aug 26, 2013 at 7:49 AM, cannifx <cann...@live.com> wrote: > Hallo! > For one of my project i want to use ActiveMQ 5.8.0, and i have following > scenario: > > Broker 1 - Sender > Broker 2 - MiddleManFirst > Broker 3 - MiddlemanSecond > Broker 4 - Receiver > > with connectors: > broker 1: > <transportConnectors> > <transportConnector name="openwire" uri="tcp://0.0.0.0:61619" > /> > </transportConnectors> > <networkConnectors> > <networkConnector name="sender-nc" > uri="static:(failover:(tcp://0.0.0.0:61610,tcp://0.0.0.0:61611 > )?randomize=false&priorityBackup=true)" > dynamicOnly="false" networkTTL="3" duplex="true"/> > </networkConnectors> > > broker 2: > <transportConnectors> > <transportConnector name="openwire" uri="tcp://0.0.0.0:61610" > /> > </transportConnectors> > <networkConnectors> > <networkConnector name="mmfirst-nc" > uri="static:(failover:(tcp://0.0.0.0:61616)?randomize=false)" > dynamicOnly="false" networkTTL="3" duplex="true"/> > </networkConnectors> > > broker 3: > <transportConnectors> > <transportConnector name="openwire" uri="tcp://0.0.0.0:61611" > /> > </transportConnectors> > <networkConnectors> > <networkConnector name="mmsecond-nc" > uri="static:(failover:(tcp://0.0.0.0:61616)?randomize=false)" > dynamicOnly="false" networkTTL="3" duplex="true"/> > </networkConnectors> > > broker 4: > <transportConnectors> > <transportConnector name="openwire" uri="tcp://0.0.0.0:61616 > "/> > </transportConnectors> > > Configuration works flawlessly as intended until i shutdown broker 2, then > i > see in log : > > WARN | Transport (tcp://0.0.0.0:61610) failed, reason: > java.net.SocketException: Connection reset, attempting to automatically > reconnect > INFO | Successfully reconnected to tcp://0.0.0.0:61611 > > but, after that only one message going through brokers, all following > messages Enqueued and Dequeued on the broker 1, i can see it in web > console, > the same behavior if i start broker 2 again, i see reconnected successfully > in log, but only 1 message going through broker 4... > > tried with last snapshot - same result. > > Any help will be appreciated > > regards, canni. > > P.S. sorry for my bad English. > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Messages-do-not-flow-through-Network-of-Brokers-after-reconnect-tp4670679.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
