It should like the underlying problem is that the slave broker isn't rejecting incoming connections (which would be a bug, so thanks for submitting the JIRA bug), but otherwise it sounds like both failover itself and shared filesystem KahaDB are working.
Can you please confirm that by making sure that clients fail over properly when the master is stopped (and not restarted) and then fail over again when the original master is started again and the new master is stopped (and not restarted)? That is, we want to make sure that failover works properly when only one broker at a time is up. Tim On Jul 24, 2017 6:35 AM, "akpuvvada" <akp4ti...@gmail.com> wrote: > > https://issues.apache.org/jira/browse/AMQ-6777 > > > > > -- > View this message in context: http://activemq.2283324.n4. > nabble.com/Active-MQ-Master-Slave-Config-Not-working- > tp4728550p4728796.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
