The persistence I'm referring to can only be set when the message is sent, so your setDeliveryMode() call is what matters, and the XML setting shouldn't matter.
Can you confirm that when you send your messages, they go to LevelDB and are stored? Also, you've never said whether this is queues or topics, durable or non-durable subscriptions, etc., and one of those combinations (non-durable topic subscriptions) are not expected to have messages after a failover. Can you describe your scenario in a little more detail? The behavior of being unable to fail over to A after the steps you listed is unexpected, and makes me think A isn't starting properly after the restart. Does the app connect if you restart the app, just not if the app stays up the whole time? Also, what is the behavior if you stop and start A when B isn't running at all? On Feb 1, 2016 12:51 AM, "BlueDragon" <shashidha...@synchronoss.com> wrote: > I did make sure of persistence both in XML and while sending message > [producer.setDeliveryMode(DeliveryMode.PERSISTENT)]. > > Its still getting lost after fail-over. > > And I observed one more thing, after the fail-over, if I stop the active > broker it does not connect back to reinstated broker. > Flow: > Before failover1 > App (connects to) --->BrokerA [BrokerB active but slave] > I restart BrokerA > After failover1 > App (connects to) --->BrokerB [BrokerA is back but as slave] > I restart BrokerB this time > Failover 2 > App (does not connect) -----X [Though BrokerA is active at this > time, > it does not recognize] > > Please guide me on how to resolve this. > > Thank you very much for the reply... > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/After-failover-earlier-messages-are-lost-tp4706630p4706713.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
