Release Highlights

Server

Enhancements

• Improve integration with Docker (#113). Problems which were previously worked around in the official Docker image, were fixed in RabbitMQ. In particular:
  • Add a way to send log messages (both "normal" and sasl messages) to stdout (#128).
  • Do not try to use exec before su ... as su(1) forks a process anyway (since 3.5.0, #129).
• Report a queue is under flow control only if it was in this situation in the last 1 second, instead of the last 5 seconds previously (#138).
• Add a check to ensure the Mnesia directory is not shared with the PID file location or the plugin expansion directory (#120). This should help users facing non-working automatic clustering.

Bug fixes

• Ensure the file handle cache remains under the memory high watermark when syncing a mirrored queue (since 2.0.0, #134).
• Restore support for messages stored on disk with the previous x-death header format (since 3.5.1, #152).
• Ensure passwords containing $ characters are properly escaped so they are not interpreted by the shell, when a password is changed using rabbitmqctl change_password (since 1.5.2, #66).

Plugin: Management UI

Enhancements

• Allow to configure rates_mode even if only rabbitmq-management-agent is enabled (rabbitmq/rabbitmq-management#33). Thanks to @databus23 for the idea and tests!

Bug fixes

• Fix a badarith crash if for some reasons, the disk free space or the file descriptors count are temporarily reported incorrectly (rabbitmq/rabbitmq-management#30).

Plugin: STOMP

Bug fixes

• Ensure the "processor" thread is terminated at the same time the "reader" thread exits (rabbitmq/rabbitmq-stomp#7). Thanks to @martink2 for the report and tests!

Client library: Java

Bug fixes

• Use a timeout to ensure a closing channel does not wait for the server forever (since 1.5.0, rabbitmq/rabbitmq-java-client#46). Thanks to @dpratt for the patch!
• Interrupt the thread when an InterruptedExceptions is caught instead of ignoring it (rabbitmq/rabbitmq-java-client#52). Thanks to @vfelberg for the report!
• Ensure the virtual host is correct in the generated URI in AMQConnection.toString() (since 1.4.0, rabbitmq/rabbitmq-java-client#42). Thanks to @dharrigan for the patch!

Documentation

• Fix documentation of Recoverable.addRecoveryListener() (rabbitmq/rabbitmq-java-client#40). Thanks to @xuwei-k for the patch!
• Fix several typos (rabbitmq/rabbitmq-java-client#39). Thanks to @xuwei-k for the patch!

Client library: .NET

Bug fixes

• Rework heartbeat handling to fix several timeout issues (rabbitmq/rabbitmq-dotnet-client#68). Thanks to @btecu for the report and tests!
• Ensure timers are destroyed when a connection is closed (since 3.5.0, rabbitmq/rabbitmq-dotnet-client#58). Thanks to @chrhlnd for the report and tests, and @mikebridge and @acquleo for the tests!
• When a channel is closed, ensure consumer dispatch for other channels are not affected (since 3.5.0, rabbitmq/rabbitmq-dotnet-client#63). Thanks to @ferviri for the patch!
• Fix a NullPointerException in MapMessageBuilder.GetContentBody() (since 3.5.0, rabbitmq/rabbitmq-dotnet-client#53). Thanks to @BrentSouza for the report!

Client library: Erlang

Enhancements

• Treat a server shutdown as an expected event and do not report an error (rabbitmq/rabbitmq-erlang-client#11). Thanks to @gotthardp for the patch!

Building and packaging

Enhancements

• Upgrade Mac OS X standalone package to Erlang/OTP 17.5 (#97).

Bug fixes

• Fix a problem where Erlang crash dumps (erl_crash.dump) were created when using the Mac OS X standalone package, even though RabbitMQ was running properly (#96). Thanks to Vitaly Numenta for the report!
• Ensure rabbit_misc:otp_release/0 returns an appropriate value when using the Mac OS X standalone package (#106).
• Ignore $RABBITMQ_PID_FILE set in /etc/rabbitmq/rabbitmq-env.conf as it would break the init script (#127).
• Ensure $RABBITMQ_PID_FILE is not used before being set in the Debian init script (since 2.8.2, #126).
• Use $(MAKE) instead of hard-coding make in the MQTT (rabbitmq/rabbitmq-mqtt#23) and STOMP (rabbitmq/rabbitmq-stomp#9) plugins.

Upgrading

To upgrade a non-clustered RabbitMQ simply install the new version. All configuration and persistent message data are retained.

To upgrade a RabbitMQ cluster, follow the instructions at:
http://www.rabbitmq.com/clustering.html#upgrading.

Source code archives

Warning: The source code archives provided by GitHub only contain the source of the broker, not the plugins or the client libraries. Please download the archives available from the official download page:
http://www.rabbitmq.com/download.html