[rabbitmq-discuss] 404, "NOT_FOUND - no queue 'foo' in vhost '/'"

Wed Jan 18 16:32:04 GMT 2012

It is important to note that the queue is durable. I just read after
sending this that none of the clients should have been allowed to
reconnect. I'm curious why two out of the three clients were able to
come up when they apparently should have also received the same error.
I will experiment some more with this knowledge about how durable
queues work. I originally wrote this assuming we would be using HA
queues and I have them on my brain...

On Jan 18, 11:24 am, Dave Stevens <daverstev... at gmail.com> wrote:
> I'm having a similar issue with 2.7.1 installed on ubuntu.
>
> I'm running a cluster of three nodes. I have three consumers consuming
> from a non-mirrored, non-exclusive queue. When I take down the node
> containing the queue with rabbitmqctl stop_app, occasionally one of
> the clients receives the following when attempting to reconnect and re-
> declare the queue.
>
> {#method<channel.close>(reply-code=404, reply-text=NOT_FOUND - no
> queue 'foo' in vhost '/', class-id=50, method-id=10),null,""}
>
> Is this a race condition caused by the clients all trying to redeclare
> the queue at the same time? I'm using the spring-amqp java client,
> although I'm probably going to ditch it soon for other reasons.
>
> On Dec 20 2011, 6:58 pm, Matt Pietrek <mpiet... at skytap.com> wrote:
>
>
>
>
>
>
>
> > Indeed! In my hour or so of testing I just did, 2.7.1 seems much happier,
> > and appears to handle VIP failover reasonably well in my scenario.
>
> > Thanks much!
>
> > Matt
>
> > On 12/20/11 3:12 PM, "Matthias Radestock" <matth... at rabbitmq.com> wrote:
>
> > >On 20/12/11 22:44, Matt Pietrek wrote:
> > >> In addition, in the rabbit@<nodename>.log, I see a whole bunch of spew,
> > >> including many instances of this:
>
> > >> =WARNING REPORT==== 20-Dec-2011::14:09:17 ===
> > >> Non-AMQP exit reason '{{{function_clause,
> > >> [{gb_trees,lookup,
> > >> [<<150,83,52,247,194,247,140,35,130,167,168,
> > >> 35,224,203,183,186>>,
> > >> {dict,0,16,16,8,80,48,
> > >> {[],[],[],[],[],[],[],[],[],[],[],[],[],
> > >> [],[],[]},
> > >> {{[],[],[],[],[],[],[],[],[],[],[],[],
> > >> [],[],[],[]}}}]},
> > >> {rabbit_amqqueue_process,
> > >> '-confirm_messages/2-fun-0-',2},
> > >> [...]
> > >> Again, this is a stock 2.7.0 install.
>
> > >The above got fixed in 2.7.1.
>
> > >Matthias.
>
> > _______________________________________________
> > rabbitmq-discuss mailing list
> > rabbitmq-disc... at lists.rabbitmq.comhttps://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-disc... at lists.rabbitmq.comhttps://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss