yep, jumped too far ahead of myself. you won't be able to listen to that on the slave, cause you won't be able to connect!
can your app have the connection string for your slave and then if master fails, just connect to the slave? On Wed, Aug 14, 2013 at 9:33 AM, deepak_a <angesh...@gmail.com> wrote: > Thanks, > > As per > http://activemq.apache.org/advisory-message.html > > I see that > ActiveMQ.Advisory.MasterBroker > is set to True (enabled by default). > > I have also added the following in my broker-config.xml > > <destinationPolicy> > <policyMap><policyEntries> > <policyEntry topic=">" advisoryForConsumed="true" /> > </policyEntries></policyMap> > </destinationPolicy> > > But I don't even see the Queue ActiveMQ.Advisory.MasterBroker in my JMX > console. > > Is there any additional config change to be done to enable the broker fire > a > message? > Another query I have is around the data-structure of the message. > The link above says #null# > > What type of information is published to the Queue? > > > regards > D > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/regarding-use-of-Advisory-messages-for-node-failure-in-a-Cluster-tp4670361p4670380.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
