that is expected. with the caveat that you would need to repeat a few times to get it delivered to all the consumers. if a message is unacked and the consumer goes away the broker will redispatch. If there are multiple consumers there is no guarantee that the same consumer gets the messages the next time. If you use a transacted session, failover will track what was consumed and not acked in a transaction and will force a rollback if the message is not replayed when you commit.
On 7 March 2014 16:18, gregg <garl...@hotmail.com> wrote: > I have been doing some Master/Slave failover testing and have encountered an > issue. > > 1) Both Master X and Slave Y broker are pointing to the same kabadb > directory > 2) I have one single message on the queue and a listener A actively > processing it (paused). Listeners B,C,D are idle. > 3) I shutdown the Master X broker > 4) Slave broker Y automatically comes online and becomes the master > 5) Consumer listeners B, C, D get reinitialized on the new master broker > > The problem is that the currently processing message gets redelivered to all > connected and idle consumers (B,C,D). Is this an invalid test approach, or > am I missing some key broker configuration? > > Thanks, > > Greg > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Same-message-redelivered-to-multiple-consumers-after-failover-tp4678640.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://redhat.com http://blog.garytully.com
