each time it is cloned.
Can you elaborate?
Thanks,
Geoff.
--
View this message in context:
http://www.nabble.com/Transactions-and-redelivery-tp25915300p25930878.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hey Mark,
We ended up opting to put the message back on the end of the queue
instead of rolling back, but this leads to repeated reprocessing of
the message. My guess is that you have solved this with metadata:
Our framework is sophisticated enough to
manage redeliveries in this way by
://www.nabble.com/Transactions-and-redelivery-tp25915300p25930878.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hi All,
When a message is rolled back on a session, it appears that no other
messages will be delivered to the consumer's listener for that session
until the original message is consumed (committed). I believe that
this is due to the session attempting to maintain message order,
however
exhaust message processing when the number of
concurrent consumers is capped.
What strategies are you using to handle this type of situation?
Thanks,
Geoff.
--
View this message in context:
http://www.nabble.com/Transactions-and-redelivery-tp25915300p25916092.html
Sent from
