Right, I haven't noticed that before. That explains strange behaviour of our system during failover tests (messages that are out of order)
kieran1 wrote: > > In my testing of this scenario, it appears that at step 9 -- 11 messages > are sent to the consumer -- there is a problem: the first of those 11 > messages is the new message sent in step 8. > > That new message should not be consumed until all of the old messages have > been consumed, right? > > I have been testing this with the same problem on both 4.0.1 and 4.0.2. > > Kieran > > -- View this message in context: http://www.nabble.com/Bug-in-failover-transport-tf2587218.html#a7593969 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
