[rabbitmq-discuss] RabbitMQ 2.4.1 Release (incl release notes)

Alexandru Scvortov alexandru at rabbitmq.com
Thu Apr 7 18:35:54 BST 2011

The RabbitMQ team is pleased to announce the release of RabbitMQ 2.4.1.

This release fixes a number of bugs, in particular one bug in 2.4.0 that
would break upgrades if durable queues were present. A notable
enhancement included in this release are cluster upgrades.

See the attached release notes for more details.

Binary and source distributions of the new release can be found in the
usual place at http://www.rabbitmq.com/download.html

We recommend that all users of earlier versions of RabbitMQ upgrade to
this latest release.

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
list at rabbitmq-discuss at lists.rabbitmq.com, or directly at
info at rabbitmq.com.

          The RabbitMQ Team

-------------- next part --------------
Release: RabbitMQ 2.4.1

Release Highlights

bug fixes
- fix breakage of upgrades when durable queues are present or
  following a non-clean shutdown
- prevent "rabbitmqctl wait" from waiting forever in certain
- the broker can be run on Erlang R12B-3 again
- some other small bug fixes

- upgrades in clusters. See
- improve memory usage when dealing with persistent messages waiting
  on acks from consumers
- better error reporting for some startup problems
- add timestamp to events published to the amq.rabbit.log exchange

java client
- remove dependency on javax.security.sasl, thus improving
  compatibility with Android and WebSphere

.net client
bug fixes
- the client can be built on .NET 2.0 again

management plugin
bug fixes
- fix issue that would cause non-admin users to be repeatedly prompted
  for their password when viewing the queues page

STOMP plugin
bug fixes
- the plugin works on Erlang R12 again

SSL authentication mechanism plugin
bug fixes
- accept SSL certificates with fields containing characters
  outside ASN.1 PrintableString (e.g. underscores)

build and packaging
bug fixes
- the OCF script works correctly when specifying an alternative
  configuration file

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 these instructions:
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 then we
recommend you contact support at rabbitmq.com for assistance with the

More information about the rabbitmq-discuss mailing list