[rabbitmq-discuss] Publisher confirms always wait for consumer ack/nack

Jerry Kuch jkuch at gopivotal.com
Wed Jan 22 21:25:22 GMT 2014

On Wed, Jan 22, 2014 at 9:07 AM, Bertrand LEMASLE <blemasle at allocine.fr>wrote:

> After reading many docs and mails on this subject (
> http://www.rabbitmq.com/confirms.html included which explains when a
> message will be confirmed), I still haven't found an answer to my question.
> When using publisher confirm (by using confirmSelect on the channel),
> messages aren't ack until they are either ack or nack by at least one
> consumer.

Totally unrelated.  The publisher confirm mechanism only goes so far as the
transfer of responsibility for a message's well being from the *publisher*
into the *broker*.

Receipt of a publisher confirm means the broker has accepted your message
and done what you asked of it, e.g. persisted it to disk, made sure it was
replicated to any applicable mirrored queues, etc.

Consumers consume from queues, and their AMQP Ack mechanism is analogous
to, in the sense of responsibility transfer, but *totally uncoupled from*
any publisher confirm happening on the inbound side.

If you really need round trip acknowledgment from producer -> broker ->
consumer -> back to producer, you need to build that into your messaging
workflow as, for example, our simple RPC over AMQP facility does.  You
might look at the tutorial examples using it, since they may directly fit
your intended use case.

Best regards,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140122/c337887b/attachment.html>

More information about the rabbitmq-discuss mailing list