Log Message:
rabbitmq: updated to 3.11.3

RabbitMQ 3.11.3

Bug Fixes

Stream unsubscription leaked metric counters.
Stream could become unavailable in certain node or network failure scenarios.

Enhancements

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

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.

CLI Tools

Bug Fixes

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.

When a plugin was enabled as a dependency (e.g. rabbitmq_shovel as a dependency \ 
of rabbitmq_shovel_management),
CLI tools previously did not discover commands in such plugins. Only explicitly \ 
enabled or pre-configured
plugins were scanned for commands.

This behavior was confusing. Now all enabled (explicitly or as a dependency) \ 
plugins are scanned.

rabbitmq-diagnostics memory_breakdown now returns results much faster in \ 
environments with a large number
of quorum queues (say, tens or hundreds of thousands).

Stream Plugin

Bug Fixes

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

AMQP 1.0 Plugin

Enhancements

Support for "modified" disposition outcome used by some client \ 
libraries (such as QPid).

Prometheus Plugin

Bug Fixes

Abruptly closed client connections resulted in incorrect updates of certain global
metric counters.

Management Plugin

Bug Fixes

Management UI links now include "noopener" and "noreferrer" \ 
attributes to protect
them against reverse tabnabbing.
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.

Shovel Plugin

Bug Fixes

Plugin could stop in environments where no static Shovels were defined and a specific
sequence of events happens at the same time.

Enhancements

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.