Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.11.3.md

RabbitMQ `3.11.3` is a maintenance release in the `3.11.x` . Please refer to the upgrade section from if upgrading from a version prior to 3.11.0. This release requires Erlang 25. 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, 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 . Stream unsubscription leaked metric counters. GitHub issue: Stream could become unavailable in certain node or network failure scenarios. GitHub issue: It is now possible to pre-configure virtual host limits for groups of virtual hosts. This is done using a set of new keys supported by `rabbitmq.conf`: ``` ini default_limits.vhosts.1.pattern = ^device defaultlimits.vhosts.1.maxconnections = 10 defaultlimits.vhosts.1.maxqueues = 10 default_limits.vhosts.2.pattern = ^system defaultlimits.vhosts.2.maxconnections = 100 defaultlimits.vhosts.2.maxqueues = -1 default_limits.vhosts.3.pattern = .* defaultlimits.vhosts.3.maxconnections = 20 defaultlimits.vhosts.3.maxqueues = 20 ``` Contributed by @illotum (AWS). GitHub issue: Quorum queue replicas no longer try to contact their unreachable peers for metrics. Previously this could result in a 30-40s delay for certain HTTP API requests that list queue metrics if one or more cluster members were down or stopped. GitHub issues: , `rabbitmq-diagnostics status` now handles server responses where free disk space is not yet computed. This is the case with nodes early in the boot process. GitHub issue: When a plugin was enabled as a dependency (e.g. `rabbitmqshovel` as a dependency of `rabbitmqshovel_management`), CLI tools previously did not discover commands in such plugins. Only explicitly enabled or plugins were scanned for commands. This behavior was confusing. Now all enabled (explicitly or as a dependency) plugins are scanned. Contributed by @SimonUnge (AWS). GitHub issue: `rabbitmq-diagnostics memory_breakdown` now returns results much faster in environments with a large number of quorum queues (say, tens or hundreds of thousands). GitHub issue: Addition of a stream member could fail if the node being added was very early in its boot process (and doesn't have a certain stream-related components started). GitHub issue: Support for "modified" disposition outcome used by some client libraries (such as QPid). GitHub issue: Abruptly closed client connections resulted in incorrect updates of certain global metric counters. GitHub issue: Management UI links now include "noopener" and "noreferrer" attributes to protect them against . Note that since management UI only includes a small number of external links to trusted resources, reverse tabnabbing is unlikely to affect most users. However, it can show up in security scanner results and become an issue in environments where a modified version of RabbitMQ is offered as a service. Contributed by @illotum (AWS). GitHub issue: Plugin could stop in environments where no static Shovels were defined and a specific sequence of events happens at the same time. Contributed by @gomoripeti (CloudAMQP). GitHub issue: Shovel now handles `connection.blocked` and `connection.unblocked` notifications from remote destination nodes. This means fewer messages are kept in Shovel buffers when a resource alarm goes into affect on the destination node. Contributed by @gomoripeti (CloudAMQP). GitHub issue: When installation directory was overridden, the plugins directory did not respect the updated base installation path. GitHub issue: `ra` was upgraded `osiris` was upgraded `seshat` was upgraded `credentials_obfuscation` was upgraded To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.11.3.tar.xz` instead of the source tarball produced by GitHub.