<div>You could write a custom middleware (to modify the queue.declares) for: <a href="https://github.com/brendanhay/myxi" target="_blank">https://github.com/brendanhay/myxi</a></div><div>Example for adding x-ha-policy: <a href="https://github.com/brendanhay/myxi/blob/master/apps/myxi/src/myxi_ha_middleware.erl" target="_blank">https://github.com/brendanhay/myxi/blob/master/apps/myxi/src/myxi_ha_middleware.erl</a></div>
<div><br></div><div>Although, as the author, I wouldn't recommend it (yet) =)</div><br><div class="gmail_quote">On Tue, Mar 27, 2012 at 12:09 PM, Simon MacMullen <span dir="ltr"><<a href="mailto:simon@rabbitmq.com" target="_blank">simon@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>On 26/03/12 17:14, Mikhail Sobolev wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I somehow overlooked the abovementioned page, thank you.<br>
<br>
Any suggestions on how to prevent stacking up the "undelivered"<br>
messages?<br>
</blockquote>
<br></div>
At the moment, the best I can suggest is to have some external process that looks for queues with 0 consumers and deletes them. Ugh.<br>
<br>
Alternatively, some sort of AMQP proxy that modifies queue.declares that don't have the "right" properties. The Java Tracer may be a starting point.<br>
<br>
But neither of these are that great. Hmm.<div><br>
<br>
Cheers, Simon<br>
<br>
-- <br>
Simon MacMullen<br>
RabbitMQ, VMware<br></div><div><div>
______________________________<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>