[rabbitmq-discuss] BASIC CONSUME kills existing queue.
Jason J. W. Williams
jasonjwwilliams at gmail.com
Sun Sep 13 03:20:13 BST 2009
Please ignore this...the queue was accidentally set to auto_delete. I apologize.
On Sat, Sep 12, 2009 at 8:15 PM, Jason J. W. Williams
<jasonjwwilliams at gmail.com> wrote:
> Usually, we're pretty good about having our consumers use a different
> user/pass than our producers. However, in testing a new app, I used
> the same for both.
> The producer would create the exchange, queue and binding and then
> publish to the exchange. So far so good. Everything is durable, and
> everything does persist through a reboot of Rabbit as expected.
> What's interesting, is if I run my test consumer, which uses the same
> user/pass, when I issue a basic_consume() Rabbit claims the queue
> doesn't exist. If I do a rabbitmqctl list_queues...sure enough the
> queue is gone.
> Is this an artifact of RabbitMQ 1.5.0?
> Thank you in advance.
More information about the rabbitmq-discuss