Re: Why message acks are not allowed after failover when using CLIENT_ACK mode

[Stephen Lau <st...@xml-asia.org>]

Hi all,

I try to break Qpid client to check the behaviour of the session dirty flag

As I see, the flag does not clean up after failover, and the session throws 
IllegalStateException when acknowledge after failover.
Does it mean something else?

Stephen


----- Original Message ----- 
From: "Rajith Attapattu" <ra...@gmail.com>
To: <de...@qpid.apache.org>
Sent: Thursday, March 12, 2009 2:37 AM
Subject: Why message acks are not allowed after failover when using 
CLIENT_ACK mode


> Hi All,
>
> Looking at the code I see that if a session is using CLIENT_ACK it
> will not allow to ack any messages after failover.
> Since we don't support full session resume it is understandable that
> messages delievered prior to failover shouldn't be allowed to ack
> after failover.
>
> But at the least new messages received after the failover should be
> allowed to ack.
> Otherwise there is no point doing failover for a session that uses
> CLIENT_ACK and we should clearly state so in our documentation.
>
> Regards,
>
> Rajith Attapattu
> Red Hat
> http://rajith.2rlabs.com/
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
> 


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org