Skip to content

Releases: rabbitmq/rabbitmq-server

RabbitMQ 3.5.3

22 May 13:55
Compare
Choose a tag to compare

Release Highlights

Server

Enhancements
  • If rabbitmqctl can't contact a node, suggest to verify any Erlang TLS distribution configuration (#162).
Bug fixes
  • Ensure the memory monitor is fully started before the file handle cache is used (since 3.5.2, #157). Before, the problem could lead to the following crash during RabbitMQ startup:

    =CRASH REPORT==== ... ===
    crasher:
      initial call: gen:init_it/6
      pid: <0.229.0>
      registered_name: []
      exception exit: {noproc,
                          {gen_server,call,
                              [vm_memory_monitor,get_memory_limit,infinity]}}
        in function  gen_server2:terminate/3 
    ...
    

    Thanks to Carl Hörberg and Gilles Danycan for the bug report!

Plugin: Management UI

Bug fixes
  • Fix a crash during RabbitMQ startup if force_fine_statistics is set in rabbitmq_management_agent configuration (since 3.5.2, rabbitmq/rabbitmq-management-agent#4). The error was:

    BOOT FAILED
    ===========
    
    Error description:
    {could_not_start,rabbit,
       {{case_clause,false},
        [{rabbit_mgmt_db_handler,ensure_statistics_enabled,0,[]},
    ...
    

    Thanks to Kevin Blackwell for the bug report!

Documentation
  • When the management UI warns about network partitions, add a link to the documentation which gives explanations and possible solutions (rabbitmq/rabbitmq-management#43).

Client library: Java

Bug fixes
Feature deprecation
  • Deprecate com.rabbitmq.client.Channel methods related to the old flow control (rabbitmq/rabbitmq-java-client#59):

    boolean flowBlocked();
    void addFlowListener(FlowListener listener);
    boolean removeFlowListener(FlowListener listener);
    void clearFlowListeners();
Documentation

Building and packaging

Bug fixes
  • When updating Git remote URLs, use git set-url ... to set the fetch URL, not git set-url --fetch ... (since 3.5.1).

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

RabbitMQ 3.5.2

12 May 16:02
Compare
Choose a tag to compare

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
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

Client library: Java

Bug fixes
Documentation

Client library: .NET

Bug fixes

Client library: Erlang

Enhancements

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

RabbitMQ 3.5.1

03 Apr 07:28
Compare
Choose a tag to compare

Release Highlights

Server

Enhancements
  • Introduce a new channel log category for channel log messages (#74).
Bug fixes
  • Ensure consumer_closed events are emitted for the actually closed channels only, not all of them (since 3.3.0, #86). The events were filtered later in the management plugin so the behaviour was correct. However, the broker did way too much work.
  • Ensure the number of x-death message headers doesn't grow indefinitely (#78). Now, there is a single entry for each {queue, reason} pair.
  • Adjust the file read buffer cache size to avoid useless reads (since 3.5.0, #69). Before this fix, reading a file backward would cause the buffer to be filled and thrown away quickly, leading to a large I/O bandwidth consumption.
  • Ensure the priority queue plugin reports its memory consumption properly (since 3.5.0, #67). Before this fix, the queue might not be paged out under memory pressure.
  • Prevent a crash while synchronising paged out priority queues (since 3.5.0, #65). This was caused by priority queues accessing message properties without checking their existence.
  • Pass the PID file to rabbitmqctl stop in rabbitmq-server.ocf, exactly like Debian- and Red Hat-flavour init scripts (since 2.6.0, #72).

Plugin: AMQP 1.0

Bug fixes

Client library: Java

Enhancements

Client library: .NET

Enhancements
Bug fixes

Building and packaging

Enhancements
Bug fixes

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

RabbitMQ 3.5.0

28 Mar 23:43
Compare
Choose a tag to compare

See release notes.

If you have any questions, please use RabbitMQ mailing list.

RabbitMQ 3.4.4

29 Mar 14:51
Compare
Choose a tag to compare

See release notes.

If you have any questions, please use RabbitMQ mailing list.

RabbitMQ 3.4.3

21 Aug 13:03
Compare
Choose a tag to compare

RabbitMQ 3.4.2

21 Aug 13:01
Compare
Choose a tag to compare

RabbitMQ 3.4.1

21 Aug 12:59
Compare
Choose a tag to compare

RabbitMQ 3.4.0

21 Aug 12:58
Compare
Choose a tag to compare

RabbitMQ 3.3.5

21 Aug 12:56
Compare
Choose a tag to compare