[rabbitmq-discuss] Error code 404 NOT_FOUND when declaring a queue in a clustered server (using .NET client)
alexandru at rabbitmq.com
Fri Feb 25 11:17:00 GMT 2011
In a cluster, if a there's a durable queue on a down'ed node,
redeclaring that queue on another node will fail with NOT_FOUND. The
only way to solve this is to bring back up the node holding the queue.
This seems to be what you're seeing, but you say all the queues were
declared on the online node. Are you sure that's the case?
Does bringing the other node up solve the problem?
Once up, can you delete the queue, redeclare it on SERVER_1, take down
SERVER_2 again and check if the problem still happens?
BTW, in the next message, you seem to have reversed SERVER_1 and
On Fri, Feb 25, 2011 at 11:57:25AM +0100, Alfonso Pantoja wrote:
> Today I've got a code=404 NOT_FOUND error when declaring a queue in a
> clustered server.
> We have 2 servers in that cluster. SERVER_1 and SERVER_2.
> The message reported that the queue the consumer wanted to declare didn't
> exist which hasn't too much sense...
> The AMQP operation
> was interrupted: AMQP close-reason, initiated by Peer, code=404,
> text="NOT_FOUND - no queue 'alfonsoqueue' in vhost '/'"
> SERVER_2 was offline and the .NET consumer tried to connect to SERVER1 (we
> don't use the array of addresses feature, we point the consumer directly to
> one single server).
> The queues were created on server SERVER_1 and there were no queues in
> webadmin queue listing of SERVER_2.
> By the way all our queues and exchanges are durable and the first thing the
> consumer do is to a
> channel.DeclareQueue(name=queue_name, durable=true)
> In the source code I see this declaration is performed using nowait=false,
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
More information about the rabbitmq-discuss