VMware

vFabric RabbitMQ 2.8.1 Release Notes

vFabric RabbitMQ 2.8.1 | 03 MAY 2012

Last Document Update: 03 MAY 2012

What's in the Release Notes

These release notes cover the following topics:

What's New in vFabric RabbitMQ

Important Note: VMware® vFabric RabbitMQ™, a commercial product, is based on open source RabbitMQ, which releases more frequently than the commercial offering. The prior vFabric RabbitMQ release is 2.4.1, and the prior open source release is 2.8.0. vFabric RabbitMQ 2.8.1 incorporates new features that were added to open source RabbitMQ 2.5.0 and later releases. The following sections highlight some of those new features and provide links to the full release notes for RabbitMQ 2.5.0 and later.

What's New in vFabric RabbitMQ 2.8.1

vFabric Rabbit RabbitMQ 2.8.1 incorporates new features from open source RabbitMQ 2.5.0 and later, as described in the sections that follow. In addition, vFabric RabbitMQ 2.8.1 resolves several issues. See Resolved Issues in vFabric RabbitMQ 2.8.1.

What's New in RabbitMQ 2.8.0

  • When you declare a queue, dead lettering enables you to specify an exchange to which messages are redirected when they are rejected or expire.
  • Internal flow control limits memory use and makes performance more predictable when the server is overloaded.
  • See also RabbitMQ 2.8.0 Release Notes.

What's New in RabbitMQ 2.7.1 and 2.7.0

RabbitMQ 2.7.1
  • Compatibility with Erlang 15B allows native operation on 64-bit Windows.
  • Deletion of exchanges or queues with many bindings is more efficient.
  • Setting for rate of change of queue lengths is added to the management API and UI.
  • Additional general improvements are made to management interface, performance, and stability.
  • See also RabbitMQ 2.7.1 Release Notes.
RabbitMQ 2.7.0
  • Messages that are requeued (as a result of an unresponsive consumer, for example) have their original order preserved.
  • Plugins are included in the main rabbitmq-server release, simplifying server configuration and upgrades. The tool rabbitmq-plugins, enables and disables plugins.
  • Clients accept an "amqp" URI scheme, which can describe all information required to connect to an AMQP server in one URI.
  • Durable queues are faster on first use and faster to recover.
  • Concurrent message storage operations for many queues are more efficient.
  • Creating a connection is faster.
  • For Java client, consumer callbacks and channel operations are threadsafe; calls to channel operations can be safely made from a Consumer method call; and consumer callback work threads can be user-supplied.
  • See also RabbitMQ 2.7.0 Release Notes.

What's New in Rabbit MQ 2.6.1 and 2.6.0

RabbitMQ 2.6.1 fixes a bug that caused a broker to fail to restart in some operating systems. See also RabbitMQ 2.6.1 Release Notes.

RabbitMQ 2.6.0
  • Active-active high availability mirrors queues on nodes in a cluster. Should one node of a cluster fail, the queue can switch automatically to one of the mirrors and continue to operate, with no unavailability of service.
  • Federation plugin offers scalable publish/subscribe messaging across WANs and administrative domains.
  • Management plugin introduces a more advanced permissions model, allowing access to information for monitoring purposes without requiring rabbit administrator permissions.
  • Stomp plugin provides a way to send and subscribe to existing AMQP queues, support temporary/reply queues, and support durable subscriptions.
  • See also RabbitMQ 2.6.0 Release Notes.

What's New in RabbitMQ 2.5.1 and 2.5.0

RabbitMQ 2.5.1 resolves a problem with upgrading from RabbitMQ 2.1.1 and 2.2.0. See RabbitMQ 2.5.1 Release Notes.

RabbitMQ 2.5.0
  • A tracing facility (firehose) for debugging incoming and outgoing messages enables you to see every message that is delivered and every message that is published.
  • New rabbitmqctl commands:
    • report: Comprehensive report of server status for support purposes.
    • environment: Displays application environment (such as config vars).
    • cluster_status: Displays cluster status (formerly part of 'status').
  • Inbound network performance is improved.
  • Routing performance is improved.
  • See also RabbitMQ 2.5.0 Release Notes.

Resolved Issues

Important Note: vFabric RabbitMQ, a commercial product, is based on open source RabbitMQ, which releases more frequently than the commercial offering. The prior vFabric RabbitMQ release is 2.4.1, and the prior open source release is 2.8.0. vFabric RabbitMQ 2.8.1 incorporates bug fixes for open source RabbitMQ 2.5.0 and later releases. The following sections highlight some of those bug fixes and provide links to the full release notes for RabbitMQ 2.5.0 and later.

Resolved Issues in vFabric RabbitMQ 2.8.1

vFabric RabbitMQ 2.8.1 incorporates the bug fixes described in the resolved issues sections for RabbitMQ 2.5.0 and later. In addition, the following issues were resolved in vFabric RabbitMQ 2.8.1:

  • Cluster RAM nodes that run an earlier version can now be upgraded successfully.
  • In the management plugin Web UI, users with only 'management' permissions no longer receive HTTP errors.
  • The rabbitmq-echopid.bat package for Windows now contains the script.

Resolved Issues in RabbitMQ 2.8.0

  • Idle CPU usage is reduced when there are many mirrored queues.
  • The server no longer stops accepting connections.
  • When all disk nodes are down, the process of starting a RAM node now fails instead of creating a blank RAM node.
  • See also RabbitMQ 2.8.0 Release Notes.

Resolved Issues in RabbitMQ 2.7.1 and 2.7.0

RabbitMQ 2.7.1

  • Promotions of high-availability slave queues to master no longer fail when using confirms.
  • High-availability queues with persistent and confirmed messages no longer have slow memory leaks.
  • Master queues now recover properly when using high-availability queues with policy of 'nodes'.
  • Frequent restart of nodes no longer causes high-availabilty queues to fail.
  • STOMP adapter: Duplicate headers are no longer generated in some MESSAGE frames; temporary reply-to queues are now re-usable; and STOMP is now compatible with Erlang R15B.
  • See also RabbitMQ 2.7.1 Release Notes.

RabbitMQ 2.7.0

  • Server startup no longer hangs when the server is trying to contact other Erlang nodes.
  • On Windows, the broker no longer crashes when some batch file variables pass unescaped backslashes to the broker.
  • See also RabbitMQ 2.7.0 Release Notes.

Resolved Issues in RabbitMQ 2.6.1 and 2.6.0

Rabbit MQ 2.6.1

  • The broker no longer fails to restart on systems that keep /var/run on a temporary file system.
  • On a busy broker, /api/nodes no longer fail with a timeout and adversely affect several management UI pages.
  • See also RabbitMQ 2.6.1 Release Notes.

RabbitMQ 2.6.0

  • Upgrading from RabbitMQ 2.1.1 to any later release no longer fails when there are durable queues with persistent messages.
  • RabbitMQ no longer fails to stop (when asked to do so) in the presence of some plug-ins, such as the shovel.
  • The presence of fast consumers on a queue no longer significantly delays the addition of new consumers.
  • Additional bug fixes improve performance.
  • See also RabbitMQ 2.6.0 Release Notes.

Resolved Issues in RabbitMQ 2.5.1 and 2.5.0

RabbitMQ 2.5.1

RabbitMQ 2.5.0

  • Recovery is simplified, improving startup times when many exchanges or bindings exist.
  • Bindings are recovered between durable queues and non-durable exchanges on restart of individual cluster nodes.
  • Performance is improved under high load and memory pressure.
  • There is now source compatibility with Erlang R14B03.
  • See also RabbitMQ 2.5.0 Release Notes.