[rabbitmq-discuss] Can't Bind After Upgrading from 3.1.1 to 3.1.5

[Chris]

Hello RabbitMQ gurus,

After upgrading a customer site from RabbitMQ 3.1.1 to 3.1.5 (on RHEL 6.2),
we had a few durable queues that did not seem to be working correctly (they
weren't receiving any messages).  It should be noted that this is a cluster
of 5 servers with queue mirroring set to exactly 2 nodes.

During troubleshooting, we deleted and recreated the queues.  After
creating the queues, we attempted to rebind them to the exchange (in the
web management GUI), but this always failed.

[In the following example, names have been changed to protect the
innocent].  After attempting to bind durable mirrored 'my.queue' to durable
direct exchange 'my.exchange' using routing key 'my.queue' (in vhost
'abc'), we get the following error:

NOT_FOUND - no binding my.queue between exchange 'my.exchange' in vhost
> 'abc' and queue 'my.queue' in vhost 'abc'


This behavior in the web console confirms the behavior we see when trying
to bind programmatically in our app (we get an AMQP 404 error).

Here is the kicker-- if we change the routing key by just one character, it
works flawlessly!  Or if we don't change anything, but add "foo=bar" to the
binding arguments, it also works!  So it seems that because we did this
binding in the past, and it was somehow corrupted, it won't allow us to
re-bind with the same arguments now.  As noted above, even after deleting
and re-creating the queue, it still won't let us do that one binding we
need.

Is there any way we can fix this easily without interrupting the customer
too much?  Or is it likely we will have to wipe mnesia on all the nodes and
rebuild the cluster (my fear is that this may be the only way)?

Is there anything I can or should do on my end to further debug /
investigate?

Thanks for your help!

-Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130920/55fae66e/attachment.htm>