Some steps to help diagnose: 1) enable debug logging for both the client and broker. org.apache.activemq=DEBUG in the log4j.properties You should see the client failover transport detect the connection failure and start retrying
2) A thread dump of the client should also show threads waiting for reconnect. This will validate that the client is doing the expected thing. On 30 March 2010 11:25, Roxana Grigore <roxananma...@yahoo.com> wrote: > > Hello Mike, > I have the same problem. I tested and re-tested and it is not working. Have > you found any solution? > > -- > View this message in context: > http://old.nabble.com/Master-Slave-issue-with-Network-of-Brokers-tp27745457p28080554.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- http://blog.garytully.com Open Source Integration http://fusesource.com
