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 2012/05/16 17:05:03 UTC
[jira] [Created] (AMQCPP-402) Fix ConnectionStateTracker
processMessageAck
Timothy Bish created AMQCPP-402:
-----------------------------------
Summary: Fix ConnectionStateTracker processMessageAck
Key: AMQCPP-402
URL: https://issues.apache.org/jira/browse/AMQCPP-402
Project: ActiveMQ C++ Client
Issue Type: Bug
Components: Openwire, Transports
Affects Versions: 3.4.2
Reporter: Timothy Bish
Assignee: Timothy Bish
Priority: Minor
Fix For: 3.5.0, 3.4.3
In ConnectionStateTracker the method that processes message acks should not be processing anything, which it doesn't by accident. Remove the code in the 3.4.x branch, and remove the method on trunk. The acks will be stale so don't track them and let rollback deal with it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (AMQCPP-402) Fix ConnectionStateTracker
processMessageAck
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQCPP-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved AMQCPP-402.
---------------------------------
Resolution: Fixed
this is fixed in trunk and the 3.4.x branch
> Fix ConnectionStateTracker processMessageAck
> --------------------------------------------
>
> Key: AMQCPP-402
> URL: https://issues.apache.org/jira/browse/AMQCPP-402
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: Openwire, Transports
> Affects Versions: 3.4.2
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Priority: Minor
> Fix For: 3.5.0, 3.4.3
>
>
> In ConnectionStateTracker the method that processes message acks should not be processing anything, which it doesn't by accident. Remove the code in the 3.4.x branch, and remove the method on trunk. The acks will be stale so don't track them and let rollback deal with it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira