Nope, this is as expected. With topics, persistence depends on the consumer. That is, you must use durable subscribers to get the result you're looking for. If there are only non-durable subs, and no previously registered durable subs, messages will not be persisted to disk and thusly will not be available on failover.
On Tue, Apr 16, 2013 at 7:17 AM, Dettol <[email protected]> wrote: > We setup a network of brokers with shared storage master/slave > < > http://fusesource.com/docs/broker/5.5/clustering/FuseMBClusterFaultTolerenceNetwork.html > > > and found that when we kill the master broker (master broker 2 in the > illustration below), the non durable topic consumer losses messages while > the slave broker is initializing. > > persistent topic ---------------- ---------------- > message producer ---->|Master Broker1| <----> |Master Broker 2|<---- non > durable > ---------------- > ---------------- topic consumer > > ---------------- > ---------------- > |Slave Broker 1| |Slave Broker > 2| > ---------------- > ---------------- > > Is this a bug (messages are sent as persistent)? > If not, what are the possible solutions in order to not loss messages in > topic during master/slave fail-over? > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Lossing-message-in-network-of-brokers-on-failover-tp4665948.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
