Details
Description
with mixed priority messages, consuming in batches, occasional async error on batched ack pre commit.
The reordering client side breaks a range ack. Disabling by default b/c when it is enabled individual ack mode is required which for transactions will negate the typical batch use case.
Attachments
Issue Links
- relates to
-
AMQ-5476 Batch transactions of priority messages: javax.jms.JMSException: Unmatched acknowledge: MessageAck {commandId = 14, responseRequired = false, ackType = 2, ...Could not find Message-ID XXX in dispatched-list (start of ack)
- Resolved