[rabbitmq-discuss] STOMP and anonymous queue deletions

Dan Di Spaltro dan.dispaltro at gmail.com
Thu Feb 19 00:40:37 GMT 2009

I am using a combination of RabbitMQ and the STOMP adapter to create a
comet application, so this means I have a few different clients
talking to rabbit.  Lets back up a bit, I am using the latest
mercurial source of the application.  The first one is the python
Twisted clients using txamqp.  For the most part everything is
straightforward and works very well on the AMQP side.  The second
piece is the javascript piece, (which is routed through orbited).

This piece is working okay.  Mainly my biggest concern is that while I
finally figured out how to use the exchanges correctly from JS and get
all my permissions lined up I now run into a new problem.  That
problem is simply that my private queues I use to route messages to on
the client side don't seem to properly getting cleaned up.  This seems
odd since I mark them in the stomp headers as auto_delete=True yet
they don't clean up.  Here is a bit of output

rabbitmqctl list_queues name auto_delete messages consumers transactions
Listing queues ...
amq.gen-53+dXDPAtlBB/wuKzyMGDg==        true    0       0       0
amq.gen-j+ewTR2zx3PQDCUCGhiWzA==        true    0       0       0
amq.gen-4ma/+dB7D+bvXpEuXWgj0A==        true    0       1       0
amq.gen-3UOPEX7YnpY1cQlG5A+qZA==        true    0       0       0

Since there are no consumers and no messages and no transactions
shouldn't queue be destroyed?  Now as a browser app, it is hard to
guarantee things being cleaned up perfectly, so should I consider a
different way of issuing a subscribe?  Below is what I use...
stomp.subscribe('', {exchange:'public-ops',
"routing_key":'public-'+session,  "auto_delete":true" });

Now I like the multicast capabilities this brings but I would like the
queue to go away once someone disconnects, is there a setting I am
missing?  Do you need more info?

Thanks for your help!

Dan Di Spaltro

More information about the rabbitmq-discuss mailing list