[ https://issues.apache.org/jira/browse/AMQ-5476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14235559#comment-14235559 ]
Gary Tully commented on AMQ-5476: --------------------------------- 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. > 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) > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: AMQ-5476 > URL: https://issues.apache.org/jira/browse/AMQ-5476 > Project: ActiveMQ > Issue Type: Bug > Components: JMS client > Affects Versions: 5.10.0 > Reporter: Gary Tully > Assignee: Gary Tully > Labels: priority, transactions > Fix For: 5.11.0 > > > with mixed priority messages, consuming in batches, occasional async error on > batched ack pre commit. > {code} > javax.jms.JMSException: Unmatched acknowledge: MessageAck {commandId = 14, > responseRequired = false, ackType = 2, consumerId = XXX, firstMessageId = > XXX, lastMessageId = XXX, destination = queue://xxx, transactionId = XXX, > messageCount = 20, poisonCause = null}; Could not find Message-ID XXX in > dispatched-list (start of ack) > at > org.apache.activemq.broker.region.PrefetchSubscription.assertAckMatchesDispatched(PrefetchSubscription.java:480){code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)