[rabbitmq-discuss] Erlang client rabbit_channel:wait_for_confirms and nacks

Michael Bridgen mikeb at squaremobius.net
Mon Nov 11 15:25:30 GMT 2013

rabbit_channel:wait_for_confirms_or_die/1 and /2 block the process
until either all messages sent since the last wait_* call have been
acked, or a nack is received in which case exit is called. Is there
any way to determine which message or messages were nacked? That might
be important.

Similarly, rabbit_channel:wait_for_confirms/1 and /2 block the process
until acks or nacks for all messages published since the last wait_*
was called. I wonder what use are they, if they don't discriminate
between acks and nacks?


More information about the rabbitmq-discuss mailing list