<div class="gmail_quote">On Wed, Jun 10, 2009 at 12:35 PM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@lshift.net">matthias@lshift.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
>From your and other peoples' comments I gather that with the default<br>
behaviour it should be possible to SEND messages to a destination even<br>
when there are no (and never have been any) subscribers for that<br>
destination. The messages should be queued and delivered to future<br>
clients when they subsequently SUBSCRIBE to that destination.<br>
<br>
Correct?</blockquote><div><br></div><div>Yes</div><div>�</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Now, declaring queues implicitly on SEND and SUBSCRIBE is all very well,<br>
but how & when do we get rid of them? Setting "auto-delete = false" has<br>
the unfortunate side effect of the queues sticking around forever, even<br>
when they have no messages or subscribers. That does not matter much if<br>
there are a finite and small(ish) number of possible destinations. But<br>
when there are many destinations, only some of which are in use at any<br>
given time, then server resources can be exhausted.<br>
<br>
I can think of various approaches to address this problem, but none are<br>
very pleasant.</blockquote><div><br></div><div>How about defaulting to auto-delete = true, but allowing one to override it in rabbitmq.conf:</div><div><br></div><div>�� � � �-rabbit</div><div>�� � � � � stomp_listeners [{"0.0.0.0",61613}]</div>
<div>�� � � � � queue_default_parameters [{"auto-delete: false"}]</div><div>�� � � � � extra_startup_steps [{"STOMP-listeners",rabbit_stomp,kickstart,[]}]</div><div><br></div><div>Or something along those lines?</div>
<div>�</div></div>