Could you possibly get around this by extending Alvaro's idea a little bit, and have consumers do a basic.reject with requeue=true on messages (queue names) consumed from the "lock" queue?<br><br><div class="gmail_quote">
On Sat, Mar 16, 2013 at 11:37 AM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com" target="_blank">matthias@rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 15/03/13 21:56, Alvaro Videla wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
- Create queues 1, 2, .... N<br>
- Bind queues to the CHX<br>
- publish the queue names to a queue called "lock" for example.<br></div>
[etc]<br>
</blockquote>
<br>
With that approach the number of consumers must be exactly the same as the number of queues; if you have fewer then some messages won't get consumed, and if you have more then some consumers won't process any messages.<br>
<br>
Furthermore, you cannot add/remove queues since that will cause some subsequent messages to get routed to different queues than prior to the queue addition/removal. They will then be picked up by different consumers.<span class="HOEnZb"><font color="#888888"><br>
<br>
Matthias.</font></span><div class="HOEnZb"><div class="h5"><br>
______________________________<u></u>_________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.<u></u>rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/<u></u>cgi-bin/mailman/listinfo/<u></u>rabbitmq-discuss</a><br>
</div></div></blockquote></div><br>