You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "John O'Hara (JIRA)" <qp...@incubator.apache.org> on 2007/01/31 02:09:33 UTC

[jira] Commented: (QPID-143) Acks during failover

    [ https://issues.apache.org/jira/browse/QPID-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468846 ] 

John O'Hara commented on QPID-143:
----------------------------------

This is like the transaction state question.
When the client is disconnected abruptly from the broker (failover or not) it must forget about all the acks that may not have been received by the server.
In theory, this means you could get duplicate deliveries on reconnection (or failover), but this is fine, since if you didn't want that you'd be using transacted sessions.

John

> Acks during failover
> --------------------
>
>                 Key: QPID-143
>                 URL: https://issues.apache.org/jira/browse/QPID-143
>             Project: Qpid
>          Issue Type: Bug
>            Reporter: Steven Shaw
>         Assigned To: Robert Greig
>
> 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.