© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Just my 3cents.
I was able to "reproduce" this problem (sometimes) in our dev Env. The binding is not lost it is just no longer working.
There are other issues with rabbitmq, replication and strange behavior under high load.
f. e. there is a small possibility for a mirrored queue to not complete replication if a node fails. This may lead to durable queues no longer be reachable, if the master node was the one which failed.
Using nondurable queues and replication on the other side may trigger the binding issue above a more often.
For both problems, deleting the queue fixes the issue. Broken bindings get cleared and nonreachable queues are re(created)