Yes, that's an appropriate way. Listen to this advisory topic on the slave:
ActiveMQ.Advisory.MasterBroker And when it becomes master, it should fire an advisory. On Wed, Aug 14, 2013 at 1:44 AM, deepak_a <angesh...@gmail.com> wrote: > Hi, > > My architecture uses Jboss+ActiveMQ (in integrated mode) > We have achieved HA (high availability) & HS (High Scalablity). > > A high level design looks like the below > > http://activemq.2283324.n4.nabble.com/ActiveMQ-Clustered-JBoss-and-JDBC-Master-Slave-td2348023.html#a2348028 > > Query is - when the primary node fails, the secondary node acquires a lock > on the database and becomes master (HA). > > Is is possible to use Advisory messages - to let know my application as to > which node has gone down and which node has acquired the lock on the > database? > > Our application displays the Queue statistics (count, depth of messages > etc) > in the UI > Intention is - if and when a node acquires a lock and becomes the Primary > node, I let the broker broadcast its IP address to the application so that > - > the app can listen to *that* specific broker's JMX to get Queue/Topic > statistics. > > Is this a right usage of Advisory messages? > > > regards > D > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/regarding-use-of-Advisory-messages-for-node-failure-in-a-Cluster-tp4670361.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
