[rabbitmq-discuss] Acked Message getting redelivered

Thu Jan 19 20:31:05 GMT 2012

If you need to have messages delivered in a at least once or exactly once
fashion I don't think there is any other way, but if you are ok with
loosing messages then looking at the redelivered flag will be much easier.
On Jan 19, 2012 5:17 PM, "Iain Hull" <iain.hull at workday.com> wrote:

> > As far as my experience goes it's correct, you have to implement it at a
> higher level.
> Yes but this is hard when messages are consumed by a cluster, they would
> have to share a single store to track processed messages or use a local
> store and ensure that certain messages are only processed by specific hosts
> in the cluster.
>
> -----Original Message-----
> From: Busoli, Simone [mailto:Simone.Busoli at ferrari.com]
> Sent: 19 January 2012 08:50
> To: Iain Hull; Eugene Kirpichov
> Cc: rabbitmq-discuss at lists.rabbitmq.com
> Subject: RE: [rabbitmq-discuss] Acked Message getting redelivered
>
> As far as my experience goes it's correct, you have to implement it at a
> higher level.
>
> -----Original Message-----
> From: rabbitmq-discuss-bounces at lists.rabbitmq.com [mailto:
> rabbitmq-discuss-bounces at lists.rabbitmq.com] On Behalf Of Iain Hull
> Sent: giovedì 19 gennaio 2012 09:46
> To: Eugene Kirpichov
> Cc: rabbitmq-discuss at lists.rabbitmq.com
> Subject: Re: [rabbitmq-discuss] Acked Message getting redelivered
>
> Thanks Eugene,
>
> From: Eugene Kirpichov [mailto:ekirpichov at gmail.com]
> > Acks are indeed asynchronous.
>
> So this means that the only reliable way to implement "at most once
> delivery" is to remember the messages uuids that you have processed, which
> won't work for clustered consumers.  Is this correct or is there another
> way to achieve this?
>
> Regards,
> Iain.
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
> _________________________________________________________________________________________________________________
> Questo messaggio è da intendersi esclusivamente ad uso del destinatario e
> può contenere informazioni che sono di natura privilegiata, confidenziale
> o non divulgabile secondo le leggi vigenti. Se il lettore del presente
> messaggio non è il destinatario designato, o il dipendente/agente
> responsabile
> per la consegna del messaggio al destinatario designato, si informa che
> ogni disseminazione, distribuzione o copiatura di questa comunicazione è
> strettamente proibita anche ai sensi del decreto legislativo 196/03 . Se
> avete ricevuto questo messaggio per errore, vi preghiamo di notificarcelo
> immediatamente a mezzo e-mail di risposta e successivamente di procedere
> alla cancellazione di questa e-mail e relativi allegati dal vostro sistema.
>
> _________________________________________________________________________________________________________________
> This message is intended only for the use of the addressee and may contain
> information that is privileged, confidential and exempt from
> disclosure under applicable law. If the reader of this message is not the
> intended recipient, or the employee or agent responsible for delivering the
> message to the intended recipient, you are hereby notified that any
> dissemination, distribution or copying of this communication is strictly
> prohibited. If you have received this e-mail in error, please notify us
> immediately by return e-mail and delete this e-mail and all attachments from
> your system.
>
> _________________________________________________________________________________________________________________
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120119/7762e5ed/attachment.htm>