<div dir="ltr">That coordination is non-trivial and very error-prone. Any reasons delivery-tag is not unique per queue? Of course we'd have to pass the queueName to Channel.basicAck() method in that case. Does AMQP allow such implementation?<div>
<br></div><div>Thanks</div><div>Behnam</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Aug 26, 2013 at 12:57 PM, Michael Klishin <span dir="ltr"><<a href="mailto:mklishin@gopivotal.com" target="_blank">mklishin@gopivotal.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Behnam Behzadi:<br>
<div class="im"><br>
> let's say we have 2 queues on one channel and each queue is consumed asynchronously by a consumer thread. If one of the consumer threads sends a bulk ack it may inadvertently end up sending ack for the messages that the other thread is consuming. Will it not?<br>
<br>
</div>Correct, with more than one consumer on a channel, you need to be careful to coordinate<br>
them if they use acks with multiple = true.<br>
--<br>
MK<br>
<br>
<br>_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
<br></blockquote></div><br></div>