Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <1710802815.1259001954089.JavaMail.jira@brutus>
Date: Mon, 23 Nov 2009 10:45:54 -0800 (PST)
From: "Gary Tully (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Resolved: (AMQ-2489) "Could not correlate acknowledgment
 with dispatched message" exception
In-Reply-To: <1858622633.1258059832742.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/activemq/browse/AMQ-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully resolved AMQ-2489.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 5.4.0

resolved in r883458 - delivery acks are only needed for unacked messages to update prefetch and expiry. When message is acked, they should be suppressed as they now are as they will result in this exception due to not found in the dispatch list.

> "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, 5.4.0
>
>         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.