[
https://issues.apache.org/activemq/browse/AMQ-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55639#action_55639
]
Gary Tully commented on AMQ-2489:
---------------------------------
thanks for the test case, The problem is a delivery ack that is not conditional
on the consumer calling acknowledge and that combined with a prefetch=1 causes
that pending delivery ack to be sent immediately, resulting in the broker error
looking for a message that has already been acked.
However the messages are being acked individually just fine.
The fix looks trivial enough, will commit once a full test run completes.
> "Could not correlate acknowledgment with dispatched message" exception
> ----------------------------------------------------------------------
>
> Key: AMQ-2489
> URL: https://issues.apache.org/activemq/browse/AMQ-2489
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.1.0, 5.3.0, 5.4.0
> Reporter: Dariusz Szablinski
> Assignee: Gary Tully
> Fix For: 5.3.1
>
> Attachments: JmsUnorderedAsynchAckTest.java
>
>
> This exception is thrown on broker side when two or more ASYNCH consumers
> acknowledges messages in not in order they received the messages.
> See more on users list:
> http://old.nabble.com/%22Could-not-correlate-acknowledgment-with-dispatched-message%22-td26308220.html
> Simple unit test attached.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
