You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2008/11/17 19:39:05 UTC
[jira] Created: (AMQ-2004) Duplicate delivery acks on failover with
transacted delivery - Async error on broker - TX has not started error on
ack
Duplicate delivery acks on failover with transacted delivery - Async error on broker - TX has not started error on ack
----------------------------------------------------------------------------------------------------------------------
Key: AMQ-2004
URL: https://issues.apache.org/activemq/browse/AMQ-2004
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.2.0
Reporter: Gary Tully
Assignee: Gary Tully
Fix For: 5.3.0
On failover transport resume, outstanding acks are delivered async. Regular consumption also delivers acks which can result in out of order delivery of outstanding delivery acks. the async delivery can occur after the regular delivery.
org.apache.activemq.transport.failover.AMQ1925Test.testAMQ1925_TXBegin modified to fail on a connection exception demonstrates this behaviour.
Solution seems to be to only deliver outstanding standard acks during deliverAcks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-2004) Duplicate delivery acks on failover with
transacted delivery - Async error on broker - TX has not started error on
ack
Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully updated AMQ-2004:
----------------------------
Attachment: AMQ-2004.patch
uploading patch for discussion pending full testing
> Duplicate delivery acks on failover with transacted delivery - Async error on broker - TX has not started error on ack
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-2004
> URL: https://issues.apache.org/activemq/browse/AMQ-2004
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.2.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 5.3.0
>
> Attachments: AMQ-2004.patch
>
>
> On failover transport resume, outstanding acks are delivered async. Regular consumption also delivers acks which can result in out of order delivery of outstanding delivery acks. the async delivery can occur after the regular delivery.
> org.apache.activemq.transport.failover.AMQ1925Test.testAMQ1925_TXBegin modified to fail on a connection exception demonstrates this behaviour.
> Solution seems to be to only deliver outstanding standard acks during deliverAcks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQ-2004) Duplicate delivery acks on failover
with transacted delivery - Async error on broker - TX has not started error
on ack
Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully resolved AMQ-2004.
-----------------------------
Resolution: Fixed
patch applied
> Duplicate delivery acks on failover with transacted delivery - Async error on broker - TX has not started error on ack
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-2004
> URL: https://issues.apache.org/activemq/browse/AMQ-2004
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.2.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 5.3.0
>
> Attachments: AMQ-2004.patch
>
>
> On failover transport resume, outstanding acks are delivered async. Regular consumption also delivers acks which can result in out of order delivery of outstanding delivery acks. the async delivery can occur after the regular delivery.
> org.apache.activemq.transport.failover.AMQ1925Test.testAMQ1925_TXBegin modified to fail on a connection exception demonstrates this behaviour.
> Solution seems to be to only deliver outstanding standard acks during deliverAcks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.