DUPS_OK_ACKNOWLEDGE vs CLIENT_ACK

[johnbing <bi...@gmail.com>]

Hi, 

I am confused between DUPS_OK_ACKNOWLEDGE and CLIENT_ACKNOWLEDGEMENT. 
I am not able to understand what is the meaning of *lazily acknowledging the
delivery of message* in case of DUPS_OK_ACKNOWLEDGE. 

where does acknowledge happens in DUPS_OK_ACKNOWLEDGE ? 

Thanks,
John



--
View this message in context: http://activemq.2283324.n4.nabble.com/DUPS-OK-ACKNOWLEDGE-vs-CLIENT-ACK-tp4674923.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: DUPS_OK_ACKNOWLEDGE vs CLIENT_ACK

[Gary Tully <ga...@gmail.com>]

lazy means doing it async and possibly in a batch (so waiting for the
next ack or some % of the prefetch) . Having received the message at
the application level does not ensure that the broker knows about the
receipt.
In the event of a connection failure, the app can think it won't see
the message again, but the broker may not have seen the ack, so the
app can get a duplicate.
In normal operation, the acks will be eventually dispatched on or
before a consumer.close

On 28 November 2013 16:34, johnbing <bi...@gmail.com> wrote:
> Hi,
>
> I am confused between DUPS_OK_ACKNOWLEDGE and CLIENT_ACKNOWLEDGEMENT.
> I am not able to understand what is the meaning of *lazily acknowledging the
> delivery of message* in case of DUPS_OK_ACKNOWLEDGE.
>
> where does acknowledge happens in DUPS_OK_ACKNOWLEDGE ?
>
> Thanks,
> John
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/DUPS-OK-ACKNOWLEDGE-vs-CLIENT-ACK-tp4674923.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.



-- 
http://redhat.com
http://blog.garytully.com