[rabbitmq-discuss] RabbitMQ stomp-adapter behaviour

[Gavin M. Roy]

On Wed, Jun 10, 2009 at 12:35 PM, Matthias Radestock <matthias at lshift.net>wrote:

> From your and other peoples' comments I gather that with the default
> behaviour it should be possible to SEND messages to a destination even
> when there are no (and never have been any) subscribers for that
> destination. The messages should be queued and delivered to future
> clients when they subsequently SUBSCRIBE to that destination.
>
> Correct?


Yes


> Now, declaring queues implicitly on SEND and SUBSCRIBE is all very well,
> but how & when do we get rid of them? Setting "auto-delete = false" has
> the unfortunate side effect of the queues sticking around forever, even
> when they have no messages or subscribers. That does not matter much if
> there are a finite and small(ish) number of possible destinations. But
> when there are many destinations, only some of which are in use at any
> given time, then server resources can be exhausted.
>
> I can think of various approaches to address this problem, but none are
> very pleasant.


How about defaulting to auto-delete = true, but allowing one to override it
in rabbitmq.conf:

        -rabbit
           stomp_listeners [{"0.0.0.0",61613}]
           queue_default_parameters [{"auto-delete: false"}]
           extra_startup_steps
[{"STOMP-listeners",rabbit_stomp,kickstart,[]}]

Or something along those lines?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20090610/163a3b1f/attachment.htm