Hi If you're using ActiveMQs master-slave then a slave will never have it's transport connector up. This is archived by a database lock or file lock or by having the slave checking the master (pure master slave). See http://activemq.apache.org/masterslave.html So you can just use the failover protocol with all possible masters (in your case failover:(tcp://serverC:61616,tcp://serverB:61616)) on your serverA
Mario On 9/21/07, LizNJ <[EMAIL PROTECTED]> wrote: > > I have a broker on one server (serverA) that needs to connect to a broker on > a set of servers (serverB or ServerC). At any given time either B or C will > be the master and the other will be slave. How can I connect my broker on A > so that once it connects to the master it does not continuously attempt to > reconnect to the slave until the master goes down. > > Liz > -- > View this message in context: > http://www.nabble.com/Connecting-To-Master-tf4498543s2354.html#a12829694 > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > >
