VMware

vFabric RabbitMQ 2.8.6 Release Notes

vFabric RabbitMQ 2.8.6 | 16 OCT 2012

Last Document Update: 06 DEC 2012

What's in the Release Notes

These release notes cover the following topics:

What's New in vFabric RabbitMQ

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.8.1, and the prior open source release is 2.8.5. vFabric RabbitMQ 2.8.6 incorporates enhancements that were added to open source RabbitMQ 2.8.2 and later releases. The following sections highlight some of those changes and provide links to the complete release notes, on the open source site, for RabbitMQ 2.8.2 and later.

What's New in vFabric RabbitMQ 2.8.6

vFabric Rabbit RabbitMQ 2.8.6 incorporates new features from open source RabbitMQ 2.8.2 and later, as described in the sections that follow. vFabric RabbitMQ 2.8.6 also resolves problems with the broker and Erlang client, as well as the management, shovel, and federation plug-ins. See Resolved Issues and the complete RabbitMQ 2.8.6 Release Notes.

As with each new release of vFabric Suite, if you use Red Hat Enterprise Linux (RHEL), you install a new VMware repository configuration RPM. This new installation enables you to easily browse and install the vFabric component RPMs associated with vFabric Suite 5.2, such as vFabric RabbitMQ 2.8.6. In addition, the 5.2 repository RPM installation now asks you immediately to accept the End User License Agreement (EULA). In previous releases, you accepted the EULA the first time you installed a vFabric component associated with the Suite release. See RHEL: Install vFabric RabbitMQ from an RPM.

For users who are installing vFabric RabbitMQ on RHEL computers or VMs, VMware provides an RPM for simplifying the Erlang installation. Under Supported Configurations and System Requirements, see "Install Erlang: Software Requirement."

The VMware RPM repository vfabric-all is deprecated and will no longer be updated with new RPMs. In addition to vFabric Suite components, vfabric-all contained releases of vFabric components that were not associated with a vFabric Suite release. If you want to install a vFabric component that is not yet part of a vFabric Suite release, you must download the RPM from the VMware Download Center and install it using rpm -ivhf. Under RHEL: Install vFabric RabbitMQ from an RPM, see "Installing vFabric RabbitMQ from a Downloaded RPM."

What's New in RabbitMQ 2.8.3, 2.8.4, and 2.8.5

These releases are primarily bug fix releases. See also Resolved Issues and the complete Release Notes for each release.

Warning: RabbitMQ 2.8.4 fixes a bug that caused log rotation to trigger a state in which the log file grows rapidly and infinitely, eventually exhausting all available disk space. If you are running RabbitMQ 2.8.3, you are strongly advised to upgrade immediately. In the meantime, do not invoke "rabbitmqctl rotate_logs". This warning applies particularly to users of the RPM and .deb packages, because these are configured to rotate logs automatically. Other versions of RabbitMQ are not affected by this bug.

What's New in RabbitMQ 2.8.2

  • RabbitMQ 2.8.2 introduces space monitoring and blocking, similar to the existing memory monitoring.
  • Performance for publishing of large messages and delivery of small messages is substantially improved.
  • The x-message-ttl value can be set to 0 (useful as an alternative to immediate-mode publish).
  • On the Java client, MulticastMain supports the multi-acknowledgment option for every N messages.
  • The management plug-in shows a large warning when running a cluster with mixed RabbitMQ and Erlang versions.
  • See the complete RabbitMQ 2.8.2 Release Notes.

Resolved Issues

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.8.1, and the prior open source release is 2.8.5. vFabric RabbitMQ 2.8.6 incorporates bug fixes that were added to open source RabbitMQ 2.8.2 and later releases. The following sections highlight some of those fixes and provide links to the complete release notes, on the open source site, for RabbitMQ 2.8.2 and later.

Resolved Issues in vFabric RabbitMQ 2.8.6

  • Shutdown of mirrored queue nodes is recorded correctly.
  • Unsupported plugins added in 2.8.5 are removed (old-federation, sockjs-erlang, cowboy, web-stomp and web-stomp-examples).
  • Removing RAM nodes from a cluster no longer leads to inconsistent state on disk nodes. Disk nodes now detect the RAM nodes' departure.
  • The Erlang client correctly accounts for file handles consumed by outgoing network connections when running as a plug-in.
  • The management plug-in prevents publication of a message with non-binary content.
  • If a failure occurs during connection establishment, both the shovel plug-in and the federation plug-in are guaranteed to continue reconnect attempts.
  • In the event of unexpected failure, the federation plug-in reports status correctly.
  • For all fixes, see the complete RabbitMQ 2.8.6 Release Notes.

Resolved Issues in RabbitMQ 2.8.5

  • Unnecessary CPU utilization no longer occurs in the presence of large numbers of idle HA queues.
  • Rapidly declaring and then deleting HA queues no longer crashes the master.
  • A race condition in the handling of node down signals was fixed, so that HA queues do not fail to restart when bringing a mirror/slave back online.
  • The test suite for the STOMP plug-in no longer fails to check for the expected number of receipts before checking whether a message had arrived successfully.
  • For all fixes, see the complete RabbitMQ 2.8.5 Release Notes.

Resolved Issues in RabbitMQ 2.8.4

  • Not specifying a suffix for a log file no longer causes the log file to grow infinitely during log file rotation.
  • rabbitmq-plugins.bat now functions correctly.
  • For all fixes, see the complete RabbitMQ 2.8.4 Release Notes.

Resolved Issues in RabbitMQ 2.8.3

  • This release incorporates several fixes to the communication protocol that underliesHA queues.
  • Deleting HA queues does not result in a memory leak.
  • A queue with many busy consumers no longer refuses to accept publishes until the queue is empty.
  • Stale transient queue information is not left behind when a node is restarted quickly.
  • Additional cluster nodes that start with insufficient disk space now accept connections after disk space increased.
  • On Debian systems, uninstalling does not fail if the broker is stopped.
  • For all fixes, see the complete RabbitMQ 2.8.3 Release Notes.

Warning: A bug in RabbitMQ 2.8.3 causes log rotation to trigger a state in which the log file grows rapidly and infinitely, eventually exhausting all available disk space. If you are running RabbitMQ 2.8.3, you are strongly advised to upgrade immediately. In the meantime, do not invoke "rabbitmqctl rotate_logs". This warning applies particularly to users of the RPM and .deb packages, because these are configured to rotate logs automatically. Other versions of RabbitMQ are not affected by this bug.

Resolved Issues in RabbitMQ 2.8.2

  • Memory leak on basic.reject{requeue = false} is fixed.
  • A queue does not fail when dead-lettering a message that has been paged to disc.
  • A memory leak with dead-letter cycles and HA queues is fixed.
  • For Debian systems, a mechanism is provided to change the FD limit.
  • For all fixes, see the complete RabbitMQ 2.8.2 Release Notes.