Public bug reported: Binary package hint: rabbitmq-server
There's a new release of RabbitMQ upstream, 1.5.5, which fixes a number of bugs reported against the 1.5.4 version that is in Jaunty. Here's a complete list of the bug fixes: - 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 There is also one small enhancement to help users in troubleshooting their setup: - display the node name and database dir in the startup message The changes are fairly small and low-risk, though quite important, particularly when running RabbitMQ in a clustered configuration. ** Affects: rabbitmq-server (Ubuntu) Importance: Undecided Status: New -- 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