[A-MQ, rollback, message order] after multiple transactions rollback, message order is not as expected
Issue
- message order can be different than expected with the following scenario:
- one consumer consuming messages from the destination
- messages are being consumed in varying size batches using a JMS transaction
- consumer rolls the transaction back multiple times and the consumer disconnects after each rollback.
Environment
- Red Hat JBoss A-MQ 6.2.1
- GA, R1, R2
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.