You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2009/10/05 15:59:31 UTC
[jira] Updated: (QPID-143) Acks during failover
[ https://issues.apache.org/jira/browse/QPID-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-143:
--------------------------------
Attachment: TEST-org.apache.qpid.test.unit.ack.AcknowledgeAfterFailoverOnMessageTest.testDupsOk.out
Attached example of this issue as generated by the AckowledgeAfterFailoverOnMessage test. The log shows teh testDupsOk test but this is the same as AutoAck.
> Acks during failover
> --------------------
>
> Key: QPID-143
> URL: https://issues.apache.org/jira/browse/QPID-143
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: M3
> Reporter: Steven Shaw
> Assignee: Martin Ritchie
> Attachments: TEST-org.apache.qpid.test.unit.ack.AcknowledgeAfterFailoverOnMessageTest.testDupsOk.out
>
>
> Martin Ritchie wrote:
> > It's possible to receive a message and before acking it, fail over to a new broker. When the message is acked the broker barfs
> > because it does not know about that message.
> See AMQChannel.checkAck.
> Steven Shaw wrote:
> > We must use NO_ACK acknowledgement mode when failover in needed as a workaround until this issue is resolved.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org