This bug was fixed in the package rabbitmq-server - 1.5.5-0ubuntu1
---------------
rabbitmq-server (1.5.5-0ubuntu1) karmic; urgency=low
* New upstream release: (LP: #380567):
- in a clustered setup, bindings to durable queues are now
correctly recovered when a queue's node restarts.
- node failure in a clustered setup could trigger premature exchange
auto-deletion
- the cluster config file name was inadvertently changed from
rabbitmq_cluster.config to cluster.config in release 1.5.4. It has
now been changed back.
- when attempting to delete a non-existing exchange, return 404
(not found), as defined by the spec, rather than 541 (internal error)
- correct some type specs to keep dialyzer happy
- display the node name and database dir in the startup message
-- Matthias Radestock <matth...@lshift.net> Tue, 26 May 2009 11:51:23
+0100
** Changed in: rabbitmq-server (Ubuntu)
Status: New => Fix Released
--
new upstream release fixes several bugs
https://bugs.launchpad.net/bugs/380567
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
--
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/universe-bugs
