see http://activemq.apache.org/shared-file-system-master-slave.html
In short, consumers should use the following URLs. If the consumers are embedded in the brokers, then using VM for the transport appears to work fine. However, if the broker goes down, so does the consumer (generally)... Consumer A failover:(vm://serverA:61616,tcp://serverB:61617) Consumer B failover:(tcp://serverA:61616,vm://serverB:61617) Vijay wrote: > > We are implementing AMQ's master/slave broker topology to achieve > geographic redundancy. > > Master is hosted on Server A and Slave is hosted on Server B. > > For geographic redundancy, we will have two consumer apps which will be > hosted on the same servers. These consumers will consume a Q named > "TEST.FOO" (an upstream system will produce the messages onto thsi Q using > master/slave failover URL). So the idea is if Server A dies, Server B > (slave) and its consumer should take over. > > here is the setup in summary: > > ServerA > ---------- > Master (tcp://master:61616) > Consumer A > > ServerB > ---------- > Slave (tcp://master:61617) > Consumer B > > 1. What URL should I use to configure both the consumers? > > 2. Can I make use of VM protocol in my case, considering broker and > consumer running on the same server to avoid tcp traffic? If yes, How does > the URL look like> > -- View this message in context: http://activemq.2283324.n4.nabble.com/Master-Slave-configuring-clients-tp3630225p3630926.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
