-of-order-redelivery-resource-adapter-tp4681601p4686656.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
ages).
Btw,
I also tried master-slave fail-over and application server fail-over while
the tool was running. Is it normal to get duplicated messages in case I kill
AMQ or the APP server with -9?
Cheers,
Tamas
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Active
'll try to provide a patch :-)
Cheers,
Tamas
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-out-of-order-redelivery-resource-adapter-tp4681601p4686618.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
set the appropriate settings on the MDB maxSessions is 1 and works fine
> when there is no exception.
>
> The problem only occurs with rollback and only in minority of the cases.
>
> Cheers,
>
> Tamas
>
>
>
> --
> View this message in context:
> http://activemq.2283
heers,
Tamas
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-out-of-order-redelivery-resource-adapter-tp4681601p4682095.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
sage 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 mai
retry.
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.
Can you elaborate? "cannot be processed by MDB" then out of delivery might
happen.
So you mean if the MDB fails and the message goes to DLQ?
On Tue, Jun 3, 2014 at 2:58 AM, Cserveny Tamas
wrote:
> Dear List!
>
> We experienced the following problem using JBoss 7 and ActiveMQ-RAR:
>
> In case a
Dear List!
We experienced the following problem using JBoss 7 and ActiveMQ-RAR:
In case a message cannot be processed by an MDB then out-of-order delivery
might happen.
We are using message grouping, still the order of the messages changes.
Does anybody has experience on enforcing strict message
