[rabbitmq-discuss] RabbitMQ 3.2.2 released
emile at rabbitmq.com
Wed Dec 11 15:58:23 GMT 2013
The RabbitMQ team is pleased to announce the release of RabbitMQ 3.2.2.
This release fixes a number of bugs in the broker (including High
Availability mode) and plugins (LDAP, Management and MQTT).
See the release notes at:
for more information.
The new release can be downloaded from:
As always, we welcome any questions, bug reports, and other feedback on
this release, as well as general suggestions for features and
enhancements in future releases. Mail us via the RabbitMQ discussion
The RabbitMQ Team
-------------- next part --------------
Release: RabbitMQ 3.2.2
25873 prevent possibility of deadlock when slaves start up (since 2.6.0)
25867 ensure automatic synchronisation does not fail when policy change
causes new slaves to start and the master to change simultaneously
25870 prevent the worker pool from running out of processes due to processes
crashing (since 1.8.0)
25899 prevent race leading to cluster upgrade failure when multiple nodes
attempt secondary upgrade simultaneously (since 2.4.1)
25912 correct reporting of flow control when connections become idle
25863 prevent channels crashing during broker shutdown (since 2.3.0)
25872 prevent empty queues from showing length as '?' after going idle
25889 ensure GET /api/overview uses consistent data types when server is idle
25920 prevent rabbitmqadmin failure when no home directory is set (since 3.2.0)
25887 prevent possible error in the presence of multiple client IDs
25905 fix handling of acks from the broker with the 'multiple' flag set
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 at
To upgrade RabbitMQ from release 2.1.0, first upgrade to 2.1.1 (all data will be
retained), and then to the current version as described above.
When upgrading from RabbitMQ versions prior to 2.1.0, the existing data will be
moved to a backup location and a fresh, empty database will be created. A
warning is recorded in the logs. If your RabbitMQ installation contains
important data then we recommend you contact support at rabbitmq.com for
assistance with the upgrade.
More information about the rabbitmq-discuss