[rabbitmq-discuss] Publisher confirms clarification

[Jerry Kuch]

See chapter 11 of RabbitMQ in Action for a nice flow chart covering how messages are handled. 

The publisher confirm goes out when what you asked for (at least) has happened. For a persistent message this means persistence to disc in any queue and any mirrors thereof it was destined for.  If circumstances are such that there was a ready, connected consumer chewing on an empty queue it's possible that the persistence will be skipped and the message directly delivered in which case the transmission of the confirm signifies this event. 

Best regards,
Jerry

Sent from my iPad.

On Feb 5, 2013, at 11:58 AM, Mark Miller <developmentalmadness at gmail.com> wrote:

> Publisher confirms define handled sucessfully as follows:
> an un-routable mandatory or immediate message is confirmed right after the basic.return;
> otherwise, a transient message is confirmed the moment it is enqueued; and,
> a persistent message is confirmed when it is persisted to disk or when it is consumed on every queue.
> 
> So my question is about the 3rd point: Is this a "whichever comes first" situation? If the message is consumed and ack'd on all queues before it gets persisted to disk then the confirmation will be sent? Or if the message is persisted to disk hasn't been ack'd then the confirm will still be sent?
> _______________________________________________
> 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/20130205/79d6a994/attachment.htm>