<div dir="ltr">That implies that <span style="font-family:arial,sans-serif;font-size:13px">delivery_tag is unique per channel, right?</span><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div>
<span style="font-family:arial,sans-serif;font-size:13px">So, how would this work if there's not a 1:1 correspondence between channels and queues and each queue has its own independent consumer thread? e.g. 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?</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">Thanks</span></div><div><span style="font-family:arial,sans-serif;font-size:13px">Behnam</span></div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Aug 26, 2013 at 9:58 AM, 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">Michael Bridgen:<br>
<div class="im"><br>
> Not quite true. basic.ack with multiple = true, *and* delivery-tag =<br>
> 0, will acknowledge all outstanding messages (on the channel).<br>
<br>
</div>My bad.<br>
<br>
With delivery_tag = N, all unacknowledged deliveries up to N will be ack-ed.<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>