[rabbitmq-discuss] RabbitMQ 1.7.2 release

Matthew Sackman matthew at lshift.net
Tue Feb 16 12:11:04 GMT 2010

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

This release fixes yet more bugs specific to Windows in regards to
memory monitoring, and works around various bat inadequacies.
Other fixes include enforcing codec size limits, and handling some
corner cases of basic.qos.

The rabbitmqctl tool has been extended with several new commands.
There have also been enhancements to the plugin system, and network
performance over high-latency links. The exception reporting in the
Java client has been improved and there are several bug fixes and
enhancements to the AMQP Tracer tool.

For details see the attached release notes.

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

Release: RabbitMQ 1.7.2

Release Highlights

bug fixes
- fix a number of problems with memory monitoring under Windows,
  including compatibility issues with versions of Erlang/OTP older
  than R13, and 64-bit versions of Windows. See the updated
  documentation at http://www.rabbitmq.com/extensions.html#memsup
- correct various path escaping bugs under Windows that could result
  in RabbitMQ failing to start
- make 'rabbitmq-multi start_all <n>' work again for n>1
- issuing a basic.qos when there are outstanding acks can no longer
  result in a higher limit than requested
- enforce codec size limits, thus preventing the server from sending
  invalid AMQP frames

- add rabbitmqctl list_channels and list_consumers commands, and add
  exclusivity information to list_queues. Also introduce a
  close_connection command to allow an administrator to selectively
  terminate client connections. See the updated admin guide at
  http://www.rabbitmq.com/admin-guide.html for details on these new
- remove the explicit setting of TCP buffer sizes in the server, thus
  allowing auto-(re)sizing to occur. This generally results in
  substantially improved throughput over high-latency links, and makes
  manual fine-tuning easier.
- introduce declarative boot sequencing, which allows plugins to be
  started at arbitrary chosen points during the sequence

Java client
bug fixes
- ensure that QueuingConsumer throws an ShutdownSignalException in
  *all* consuming threads, not just one
- fix race conditions in 'tracer' tool that could cause it to fail

- make exception stack traces more meaningful
- allow overriding of several RpcClient methods, for easier extension
  and re-use
- improve performance of channel creation for high channel counts
- improve performance of 'tracer' tool
- add option to 'tracer' tool to suppress content bodies, which is
  useful for tracing connections carrying a high data volume
- better exception reporting in 'tracer' tool

.net client
- improve performance of channel creation for high channel counts

building & packaging
bug fixes
- under macports, ensure env var settings are passed to the various
  startup and control scripts

The database schema has not changed since the 1.6.0 release, so user
accounts, durable exchanges and queues, and persistent messages will
all be retained during the upgrade.

If, however, you are upgrading from a release prior to 1.6.0, when the
RabbitMQ server detects the presence of an old database, it moves it
to a backup location, creates a fresh, empty database, and logs a
warning. 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