[rabbitmq-discuss] RabbitMQ publisher confirms behaviour

[Simon MacMullen]

On 26/06/13 23:57, Rohit Yadav wrote:
> What happens when a durable message is published with publisher confirms
> and the producer is stopped, i.e. we don't know if a confirm was
> received. In such a case if the message reaches the broker but the
> broker fails to send confirms back, is the message dropped?

No.

> When I stop
> the consumer I wait to receive any leftover confirms and I see that even
> after say 60s the _deliveries is not empty. How may I make sure messages
> which were sent confirm asynchronously and if I should wait for sometime
> before closing the channel how may I determine the wait time period?

You should get confirms back quickly. The confirm is *not* an indication 
that the message has been consumed, it means the broker has taken 
responsibility for the message.

> How does confirms work internally at the broker level, as in the latest
> RabbitMQ server.

See http://www.rabbitmq.com/confirms.html#when

Cheers, Simon

-- 
Simon MacMullen
RabbitMQ, Pivotal