Okay found out something during my experiments. When in master slave - replication mode, then we have to know which has the latest data. If both master and slave are down. Then configure the one with the latest data as the master and the other one slave. Then turn them back on and the re-connection occurs properly.
Other wise we have to deploy shared storage strategy, where this is all done automatically i guess. -- View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-cluster-reconnection-tp4715113p4715439.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
