You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2009/11/23 20:33:52 UTC
[jira] Created: (AMQCPP-270) Broker exception on message Ack,
Broker exception on message Ack,
---------------------------------
Key: AMQCPP-270
URL: https://issues.apache.org/activemq/browse/AMQCPP-270
Project: ActiveMQ C++ Client
Issue Type: Bug
Affects Versions: 3.0.1
Reporter: Timothy Bish
Assignee: Timothy Bish
Fix For: 3.1
Certain cases that involved acknowledging a message from the async callback of a MessageListener when in Client or Individual Ack modes can result in this error from the broker: "Could not correlate acknowledgment with dispatched message"
This is the same situation as documented in AMQ-2489
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQCPP-270) Broker exception on message Ack,
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved AMQCPP-270.
---------------------------------
Resolution: Fixed
Fixed in trunk.
> Broker exception on message Ack,
> ---------------------------------
>
> Key: AMQCPP-270
> URL: https://issues.apache.org/activemq/browse/AMQCPP-270
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Affects Versions: 3.0.1
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Fix For: 3.1
>
>
> Certain cases that involved acknowledging a message from the async callback of a MessageListener when in Client or Individual Ack modes can result in this error from the broker: "Could not correlate acknowledgment with dispatched message"
> This is the same situation as documented in AMQ-2489
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.