Thanks for the replies. The reason we have redundant clients is to survive hardware crash as both broker and client reside on the same machine.
We keep the Client 2 live to just keep trying for connection to slave until master goes down. Once slave becomes master, it gets connection and starts processing. coming to original Question. Server1 -------- Master - standalone JMS Client 1 I want to handle a rare scenrio. Obvisouly Master broker, client run in two diffrent OS processes. If Master process dies for some X reason, I want to shutdown the client as well. Probably will give out a try with Transport listener. Before killing the standalone JMS client 1 programmaticlly, I would also like to check if the slave Broker actually became Master (just as a double check) in addition to Transport listener way. How can I verify this programatically given that I have just broker url for slave.. -- View this message in context: http://activemq.2283324.n4.nabble.com/Master-slave-configuration-tp3621735p3621817.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
