new upstream release fixes several bugs
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| rabbitmq-server (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
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_
- 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.
| Matthias Radestock (matthias-lshift) wrote | #1 |
| Matthias Radestock (matthias-lshift) wrote | #2 |
| Matthias Radestock (matthias-lshift) wrote | #3 |
| Matthias Radestock (matthias-lshift) wrote | #4 |
| Daniel Holbach (dholbach) wrote | #5 |
| Launchpad Janitor (janitor) wrote | #6 |
| Changed in rabbitmq-server (Ubuntu): | |
| status: | New → Fix Released |
You overwrote a lot of debian/changelog - I reverted to the old changelog and added your entry. Also I changed jaunty to karmic.
If you want to get it into jaunty, check out https:/