vFabric RabbitMQ 2.4.1 Release Notes
vFabric RabbitMQ 2.4.1 | 14 SEPT 2011
Last Document Update: 14 SEPT 2011
What's in the Release Notes
These release notes cover the following topics:
What's New in RabbitMQ 2.4.1
This release of vFabric RabbitMQ contains the following enhancements:
- Cluster upgrades. Under Clustering, see "Upgrading Clusters."
- Improved memory usage for persistent messages waiting on acks from consumers.
- Better error reporting for some startup problems.
- Addition of timestamp to events published to the amq.rabbit.log exchange.
Java Client Enhancements
- The dependency on javax.security.sasl has been removed, thus improving the compatibility with Android and WebSphere.
The following issues have been resolved in this release:
- Server: Breakages in upgrades when durable queues are present or following a non-clean shutdown no longer occur.
- Server: rabbitmqctl wait in certain circumstances no longer waits forever.
- Server: The broker can be run on Erlang R12B-3 again.
- .NET Client: The client can be built on .NET 2.0 again.
- Management Plugin: Non-admin users are no longer repeatedly prompted for their password when viewing the queue page.
- STOMP Plugin: The plug-in works on Erlang R12 again.
- SSL Authentication Mechanism Plugin: The plug-in now accepts SSL certificates with fields that contain characters outside ASN.1 PrintableString (for example, underscores).
- Build and Packaging: The OCF script works correctly when an alternative configuration file is specified.
To upgrade a non-clustered RabbitMQ from release 2.1.1 or later, simply install the new version. All configuration and persistent message data is retained.
To upgrade a clustered RabbitMQ from release 2.1.1 or later, install the new version on all the nodes and follow the instructions under "Upgrading Clusters" in Clustering. All configuration and persistent message data is retained.
To upgrade a non-clustered RabbitMQ from release 2.1.0, first upgrade to 2.1.1 (which retains all data), and then to the current version as described above.
To upgrade a clustered RabbitMQ prior to 2.1.1 or a stand-alone broker from releases prior to 2.1.0, if the RabbitMQ installation does not contain any important data, then simply install the new version. RabbitMQ will move the existing data to a backup location before creating a fresh, empty database. A warning is recorded in the logs. If your RabbitMQ installation contains important data, it is recommended that you contact VMware Support for assistance with the upgrade.