Releases: rabbitmq/rabbitmq-server
RabbitMQ 3.5.5 RC2
Release Highlights
This is the second release candidate of RabbitMQ 3.5.5. We release it earlier than expected because of a problem with the RC1 files on GitHub (see the RC1 release notes). It contains only some code cleanup compared to RC1; see 3.5.5 RC1 release notes for other changes since RabbitMQ 3.5.4.
Server
Enhancements
- Cleanup code in
rabbit_variable_queue
(#301, #304), following all the optimization brought to this module.
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 archive
Warning: The source code archive provided by GitHub only contains the source of the broker only, not the plugins. Please download the archive named rabbitmq-server-3.5.4.902.tar.gz
.
RabbitMQ 3.5.5 RC1
Release Highlights
This is the first release candidate of RabbitMQ 3.5.5. Beyond the usual bug fixes, it brings nice speed improvements when a queue pages messages to disk.
Release artifacts use "3.5.4.901" as the release number and not eg. "3.5.5-rc1" because of a limitation in our .NET client packaging; it expects digits only. So ".901" stands for RC 1, ".902" for RC 2, and so on.
IMPORTANT: Release files were removed because they are invalid! We tried to upload the correct files, but the old versions are still served. To workaround this problem, the second release candidate will be released shortly. Please do not use the RC 1 files you downloaded: they correspond to the development branch (ie. the nightly release), not the 3.5.x stable branch!
Server
Enhancements
-
Improve performance when a queue's journal is written to the disk (#227, #289). With previous versions of RabbitMQ, this could block the queue even when it wasn't I/O bound.
The default queue index journal size was also reduced from 65536 to 32768 entries (#279). This also helps normalize throughput.
-
Improve performance when a queue is purged (#295).
-
Introduce new options to tune the queue paging performance (#284). These are low-level settings and should be handled carefully. Here are the default values:
%% In /etc/rabbitmq/rabbitmq.config [ {rabbit, [ {credit_disc_bound, {2000, 500}}, {io_batch_size, 2048} ]} ].
-
Add an option to disable
file_handle_cache
's read cache (#226). This read cache was reported to be a performance penalty, especially when a starting RabbitMQ slave needs to synchronize and fetch messages from a master node. We now offer an option to disable this cache and we plan to disable it by default in RabbitMQ 3.6.0. Here is how to use this new option:%% In /etc/rabbitmq/rabbitmq.config [ {rabbit, [ {fhc_read_buffering, false} ]} ].
-
The
queue_index_embed_msgs_below
parameter is now read once from the application environment when the queue is created, instead of every time it is needed (#291). This removes a bottleneck by avoiding synchronous calls to the Erlang application server. -
Reduce default heartbeat interval from 580 to 60 seconds (#297). This is a more sensible default value, after considering what users usually do.
-
Force essential TCP options (#282), especially
{reuseaddr, true}
. User won't have to copy them when tuning TCP options anymore and this decreases the risk of errors. -
Catch
SIGTERM
and other signals in therabbitmq-server
script to stop RabbitMQ gracefully (#234). This mostly targets Docker users. -
Honor
!RABBITMQ_BASE!
value for the default location ofrabbitmq-env-conf.bat
(#239). -
Warn user if a 32-bit Erlang runtime is used (#251), due to the limited address space and the possible memory shortage.
Bug fixes
- Fix a queue hang when a slave node is lost (#224).
- Fix a crash during startup when RabbitMQ tries to clean non-existing bindings (#235).
- Fix how
NODE_IP_ADDRESS
andNODE_PORT
are handled inrabbitmq-env.bat
on Windows (#243, #288). This bug made it impossible to override TCP listen port, for example. - Fix a problem in
gen_server2
causing calls to timeout under certain conditions (#268). - Support old version of GNU sed (#273).
Plugin: Federation
Bug fixes
- Fix a crash when certain headers are already present in the forwarded message (rabbitmq/rabbitmq-federation#12).
- Increase reconnection delay from 1 to 5 seconds (rabbitmq/rabbitmq-federation#15). This reduces the noise in the SASL log file.
- Ignore federation-specific headers added by clients (rabbitmq/rabbitmq-federation#16).
Plugin: Management UI
Enhancements
- Do not consider no-UTF-8 content as invalid (rabbitmq/rabbitmq-management#48). Now, the plugin just mentions why it cannot display it.
- Split long Base64 content in multiple lines (rabbitmq/rabbitmq-management#49).
Bug fixes
- Fix a bug with rounding moving averages (rabbitmq/rabbitmq-management#35). This caused absurd values to be displayed.
Plugin: STOMP
Bug fixes
- Properly propage extensions headers (
x-headers
) in theSUBSCRIBE
andSEND
frames (rabbitmq/rabbitmq-stomp#16). This allows a STOMP client to set parameters such as TTL, queue maximum length, and so on.
Client library: Java
Bug fixes
- Stop recovery when a client is closed (rabbitmq/rabbitmq-java-client#77).
- Make connection handshake timeout configurable (rabbitmq/rabbitmq-java-client#81).
Client library: .NET
Bug fixes
- Handle
ObjectDisposed
exceptions gracefully when re-scheduling timers (rabbitmq/rabbitmq-dotnet-client#118). - Do not throw exceptions from a
Dispose
method (rabbitmq/rabbitmq-dotnet-client#119).
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 archive provided by GitHub only contains the source of the broker, not the plugins or the client libraries. Please download the archive named rabbitmq-3.5.4.901.tar.gz
.
RabbitMQ 3.5.4
This release contains bug fixes and minor usability improvements.
RabbitMQ Server
Enhancements
rabbitmq-env.conf.bat Support on Windows
It is now possible to use a separate file for configuring RabbitMQ environment variables on Windows.
Excessive SASL Logging on Windows
SASL logger was needlessly verbose on Windows, even when configured to only log
errors.
warn
as Alias to warning
When configuring log levels, warn
can now be used as an alias for warning
.
rabbitmqctl purge_queue
rabbitmqctl purge_queue
is a new rabbitmqctl
command which purges a queue and can
be used in situations when rabbitmqadmin
or management UI are not available.
file_handle_cache:clear_read_cache/0
file_handle_cache:clear_read_cache/0
is a new function that clears read cache buffers.
It is meant to be used with rabbitmqctl eval
.
Improved rabbitmqctl Error Messages
When rabbitmqctl list_user_permissions
is invoked without any arguments, it now outputs
a sensible error message.
Kernel Polling Enabled Unconditionally by Default
Previously it was possible to accidentally disable runtime kernel polling (epoll, kqueue, etc) by
overriding RABBITMQ_SERVER_ERL_ARGS
. Now kernel polling is always enabled unless
explicitly disabled using RABBITMQ_SERVER_ADDITIONAL_ERL_ARGS
.
Easier I/O Thread Pool Size Configuration
Runtime I/O thread pool size is now easier to tweak: just use the RABBITMQ_IO_THREAD_POOL_SIZE
environment variable.
Higher I/O Thread Pool Size Default
Runtime I/O thread pool size is now 64
instead of 30
by default. This reduces time spent waiting for
file I/O operations to complete on machines with 8 or more cores.
Improved Heartbeat Timeout Logging
Heartbeat timeouts are now logged with clearer messages and mention effective
timeout value.
rabbitmq-server#159
Bug Fixes
Recoverable Mirror Could Be Reset Due to Race Condition
Recoverable mirror could be reset (considered to be unrecoverable) on start
due to a race condition.
rabbitmq-server#200, since 3.5.0
.
Throughput Regression Fix
rabbitmq-server#191, since 3.4.0
.
x-death
headers can now safely be republished by clients
When a client republished an x-death
event injected during dead-lettering, it could lead
to queue process termination.
rabbitmq-server#216, since 3.5.2
.
STOMP Plugin
Enhancements
Test Suite Upgraded to Stomp.py 4.x
Test suite now uses the most recent Stomp.py version.
End Frame With a Newline Character
STOMP frames are now terminated with a newline character.
This is allowed by the STOMP spec and improves compatibility with the PHP STOMP extension.
Java Client
Enhancements
Queue Name Length Validated Early
Queue names longer than 255 characters (per protocol spec) now result in an IllegalArgumentException
thrown early and with a clear error message.
Forgiving Exception Handler
Default ExceptionHandler
implementation closes the channel after an unhandled consumer exception.
This is not desirable in every case, so a new ForgivingExceptionHandler
was introduced. It works
exactly as DefaultExceptionHandler
but does not close the channel.
Bug Fixes
Memory Leak
TCP back pressure added to the client in the 3.5.0
cycle had a memory leak that manifested itself
when channel churn was high.
rabbitmq-java-client#69, since 3.5.0
.
.NET Client
Bug Fixes
Framing Errors When Publishing During Flow Control
Several clients (including the .NET one) had a subtle socket write failure handling issue that resulted in incorrect
frame interleaving errors when (temporary) flow control kicked in in the server.
rabbitmq-server#156, since 1.0.0
.
Heartbeat Implementation Fixes
Several issues around heartbeats are fixed. They resulted in the client failing to send heartbeat
frames on time and being disconnected on idle connections, in particular when TLS was enabled.
rabbitmq-dotnet-client#82, since 3.5.2
.
rabbitmq-dotnet-client#100, since 3.5.2
.
Fixed Memory Leak in Automatically Recovering Connections
rabbitmq-dotnet-client#109, since 3.4.0
.
Explicit Connection.Close Prevents Automatic Recovery Attempts
Explicitly invoked Connection.Close
or Connection.Abort
will disable ongoing and future automatic
connection recovery attempts.
rabbitmq-dotnet-client, since 3.4.0
.
Subscription.Close Hangs if Queue is Deleted Underneath It
Subscription.Close()
used to hang if the queue it was consuming from was previously
deleted.
rabbitmq-dotnet-client#89, since 1.0.0
.
RabbitMQ 3.5.4 RC2
This release candidate contains bug fixes and minor usability improvements.
RabbitMQ Server
Enhancements
rabbitmq-env.conf.bat Support on Windows
It is now possible to use a separate file for configuring RabbitMQ environment variables on Windows.
Excessive SASL Logging on Windows
SASL logger was needlessly verbose on Windows, even when configured to only log
errors.
warn
as Alias to warning
When configuring log levels, warn
can now be used as an alias for warning
.
rabbitmqctl purge_queue
rabbitmqctl purge_queue
is a new rabbitmqctl
command which purges a queue and can
be used in situations when rabbitmqadmin
or management UI are not available.
file_handle_cache:clear_read_cache/0
file_handle_cache:clear_read_cache/0
is a new function that clears read cache buffers.
It is meant to be used with rabbitmqctl eval
.
Improved rabbitmqctl Error Messages
When rabbitmqctl list_user_permissions
is invoked without any arguments, it now outputs
a sensible error message.
Kernel Polling Enabled Unconditionally by Default
Previously it was possible to accidentally disable runtime kernel polling (epoll, kqueue, etc) by
overriding RABBITMQ_SERVER_ERL_ARGS
. Now kernel polling is always enabled unless
explicitly disabled using RABBITMQ_SERVER_ADDITIONAL_ERL_ARGS
.
Easier I/O Thread Pool Size Configuration
Runtime I/O thread pool size is now easier to tweak: just use the RABBITMQ_IO_THREAD_POOL_SIZE
environment variable.
Higher I/O Thread Pool Size Default
Runtime I/O thread pool size is now 64
instead of 30
by default. This reduces time spent waiting for
file I/O operations to complete on machines with 8 or more cores.
Improved Heartbeat Timeout Logging
Heartbeat timeouts are now logged with clearer messages and mention effective
timeout value.
rabbitmq-server#159
Bug Fixes
Recoverable Mirror Could Be Reset Due to Race Condition
Recoverable mirror could be reset (considered to be unrecoverable) on start
due to a race condition.
rabbitmq-server#200, since 3.5.0
.
Throughput Regression Fix
rabbitmq-server#191, since 3.4.0
.
x-death
headers can now safely be republished by clients
When a client republished an x-death
event injected during dead-lettering, it could lead
to queue process termination.
rabbitmq-server#216, since 3.5.2
.
STOMP Plugin
Enhancements
Test Suite Upgraded to Stomp.py 4.x
Test suite now uses the most recent Stomp.py version.
Java Client
Enhancements
Queue Name Length Validated Early
Queue names longer than 255 characters (per protocol spec) now result in an IllegalArgumentException
thrown early and with a clear error message.
Forgiving Exception Handler
Default ExceptionHandler
implementation closes the channel after an unhandled consumer exception.
This is not desirable in every case, so a new ForgivingExceptionHandler
was introduced. It works
exactly as DefaultExceptionHandler
but does not close the channel.
Bug Fixes
Memory Leak
TCP back pressure added to the client in the 3.5.0
cycle had a memory leak that manifested itself
when channel churn was high.
rabbitmq-java-client#69, since 3.5.0
.
.NET Client
Bug Fixes
Framing Errors When Publishing During Flow Control
Several clients (including the .NET one) had a subtle socket write failure handling issue that resulted in incorrect
frame interleaving errors when (temporary) flow control kicked in in the server.
rabbitmq-server#156, since 1.0.0
.
Heartbeat Implementation Fixes
Several issues around heartbeats are fixed. They resulted in the client failing to send heartbeat
frames on time and being disconnected on idle connections, in particular when TLS was enabled.
rabbitmq-dotnet-client#82, since 3.5.2
.
rabbitmq-dotnet-client#100, since 3.5.2
.
Fixed Memory Leak in Automatically Recovering Connections
rabbitmq-dotnet-client#109, since 3.4.0
.
Explicit Connection.Close Prevents Automatic Recovery Attempts
Explicitly invoked Connection.Close
or Connection.Abort
will disable ongoing and future automatic
connection recovery attempts.
rabbitmq-dotnet-client, since 3.4.0
.
Subscription.Close Hangs if Queue is Deleted Underneath It
Subscription.Close()
used to hang if the queue it was consuming from was previously
deleted.
rabbitmq-dotnet-client#89, since 1.0.0
.
RabbitMQ 3.5.3
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 inrabbitmq_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
- During handshake, await on continuations with a timeout (rabbitmq/rabbitmq-java-client#65). Unfortunately, this change breaks the API. Thanks to @jhalterman for the bug report and testing!
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
- Revisit
com.rabbitmq.client.Channel
documentation (rabbitmq/rabbitmq-java-client#60, rabbitmq/rabbitmq-java-client#30, rabbitmq/rabbitmq-java-client#32). - Improve documentation around recovery listeners (rabbitmq/rabbitmq-java-client#35).
Building and packaging
Bug fixes
- When updating Git remote URLs, use
git set-url ...
to set the fetch URL, notgit 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
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:
- 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 usingrabbitmqctl change_password
(since 1.5.2, #66).
Plugin: Management UI
Enhancements
- Allow to configure
rates_mode
even if onlyrabbitmq-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
inMapMessageBuilder.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-codingmake
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
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
inrabbitmq-server.ocf
, exactly like Debian- and Red Hat-flavour init scripts (since 2.6.0, #72).
Plugin: AMQP 1.0
Bug fixes
- Fix heartbeats (rabbitmq/rabbitmq-amqp1.0#6).
- Respond with a protocol error if a disposition frame is incorrect (rabbitmq/rabbitmq-amqp1.0#8).
- Fix a crash if the
initial-delivery-count
is not 0 (rabbitmq/rabbitmq-amqp1.0#9).
Client library: Java
Enhancements
- Uplift
RecoveryAwareAMQConnection
andRecoveryAwareChannelManager
to useConnectionFactory
's custom threadFactory (rabbitmq/rabbitmq-java-client#33).
Client library: .NET
Enhancements
- Make
IQueueingBasicConsumer
andISubscription
public (rabbitmq/rabbitmq-dotnet-client#47). - Add a test case to ensure consumers are properly resumed after automatic recovery (rabbitmq/rabbitmq-dotnet-client#50).
Bug fixes
- Ensure no bindings are lost during automatic recovery (since 3.4.0, rabbitmq/rabbitmq-dotnet-client#43).
- Ensure client certificates are not mandatory with SSL connections (rabbitmq/rabbitmq-dotnet-client#46). There was a previous attempt in fixing this but it broke the ability to require specific SSL versions (since 3.5.0, rabbitmq/rabbitmq-dotnet-client#44).
- Ensure
ConsumerWorkService
uses the scheduler it is constructed with (since 3.5.0, rabbitmq/rabbitmq-dotnet-client#40).
Building and packaging
Enhancements
- Teach
make checkout
to retry if GitHub closes the connection (rabbitmq/rabbitmq-public-umbrella#17). - Add
make sync_gitremote
andmake sync_gituser
targets to synchronize Git remote and user/email accross the umbrella and all its subrepositories (rabbitmq/rabbitmq-public-umbrella#5).
Bug fixes
- Make internal database files private to the group (eg.
rabbitmq
) (#68). - Improve
make up_c
to work with detached HEAD. This allows to checkout a tag again (since 3.5.0, rabbitmq/rabbitmq-public-umbrella#6). - Fix
make status
so it walks through directories correctly (rabbitmq/rabbitmq-public-umbrella#13). - Use
$(MAKE)
instead of a hard-codedmake
inmake plugins-srcdist
(rabbitmq/rabbitmq-public-umbrella#18).
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
See release notes.
If you have any questions, please use RabbitMQ mailing list.
RabbitMQ 3.4.4
See release notes.
If you have any questions, please use RabbitMQ mailing list.
RabbitMQ 3.4.3
See release notes at http://www.rabbitmq.com/release-notes/README-3.4.3.txt