You'll have to check the settings on the MDB. You may have multiple concurrent sessions? Or multiple sessions? ActiveMQ by default will retry at the consumer level so you shouldn't end up with that.
On Thu, Jun 5, 2014 at 6:41 AM, smil2k <[email protected]> wrote: > Hi, > > In case the MDB throws an exception, then a mixup might happen. > > Example: Let's assume 3 messages. > > In case 1 throws an exception, my expectation would be this: > > 1 1retry 2 3 > > But in reality the following happens in a minority case: > > 1 2 1retry 3 > > So message 2 is processed before the 1retry. > > Cheers, > > Tamas > > > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-out-of-order-redelivery-resource-adapter-tp4681601p4681719.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
