By default, the failover transport attempts to connect to the child URIs in order. That doesn't mean it considers the first one to be the master, just that it tries the first one first.
When the client doesn't attempt to connect to the secondary broker, that means it's successfully connecting to the first broker. That means that either the first broker failed to shut down (the logs may tell you why), or it shut down fine but you brought it back up and it failed to detect that the second broker was the master (which would mean you haven't set up the shared filesystem KahaDB correctly). Tim On Jul 14, 2017 5:12 AM, "akpuvvada" <akp4ti...@gmail.com> wrote: > I observed an issue with the Fault Tolerance configuration: > When the primary/master is down, clients are not able to reconnect to the > secondary on retry; it is throwing a warning and trying to reconnect. Also, > it is considering the first URL as Master and first trying to connect to > and > fall back is not working even if we stop the Master and restart the client. > The fail-over URL has to be changed to make the connection work such that > the Machine 2 (current master) tcp URL is the first one. > > I configured the Fault Tolerance as per > http://activemq.apache.org/shared-file-system-master-slave.html > Shared File System - > <persistenceAdapter> > <kahaDB directory="/sharedFileSystem/sharedBrokerData"/> > </persistenceAdapter> > > Please help me identify where I am ding wrong. > I am using URL : failover:(tcp://host1:61616,tcp:/host2:61616) > > Appreciate any help. > > > > -- > View this message in context: http://activemq.2283324.n4. > nabble.com/Active-MQ-Master-Slave-Config-Not-working-tp4728550.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
