RabbitMQ 3.11.27
is a maintenance release in the 3.11.x
release series.
This release series is no longer covered by community support.
Please refer to the upgrade section from v3.11.0 release notes if upgrading from a version prior to 3.11.0.
This release requires Erlang 25 and supports Erlang versions up to 25.3.x
.
RabbitMQ and Erlang/OTP Compatibility Matrix has more details on
Erlang version requirements for RabbitMQ.
As of 3.11.0, RabbitMQ requires Erlang 25. Nodes will fail to start on older Erlang releases.
Erlang 25 as our new baseline means much improved performance on ARM64 architectures, profiling with flame graphs across all architectures, and the most recent TLS 1.3 implementation available to all RabbitMQ 3.11 users.
Release notes can be found on GitHub at rabbitmq-server/release-notes.
-
Avoids a rare exception that could stop TCP socket writes on a client connection.
-
Definition files that are virtual host-specific cannot be imported on boot. Such files will now be detected early and the import process will terminate after logging a more informative message.
Previous the import process would run into an obscure exception.
-
Avoids two Shovels being started after an upgrade from
3.11.25
or older versions.Two Shovels running concurrently would still transfer messages but because they act as competing consumers (and publishers), this affected message ordering in the target queue.
Contributed by @gomoripeti (CloudAMQP).
-
DELETE /api/policies/{vhost}/{policy}
returned a 500 response instead of a 404 one when target virtual host did not exist.GitHub issue: #9983
None in this release.
To obtain source code of the entire distribution, please download the archive named rabbitmq-server-3.11.27.tar.xz
instead of the source tarball produced by GitHub.