Log Message:
rabbitmq: updated to 3.11.13

RabbitMQ 3.11.13

Core Server

Bug Fixes

3.11.12 introduced a regression that caused client connections to fail with an \ 
exception
when TCP or TLS listeners were bould to a particular interface.

RabbitMQ 3.11.12

Core Server

Bug Fixes

Boot time import of definitions from a conf.d-style directory failed unless
definitions.skip_if_unchanged was set to true, for example, like in this
rabbitmq.conf:

definitions.skip_if_unchanged = false
definitions.import_backend = local_filesystem
definitions.local.path = /path/to/RabbitMQ/definitions/conf.d/

Improved resiliency of dead-lettering.

Enhancements

When the maximum allowed number of connections to the node was limited using the \ 
connection_max key
and the limit was reached, newly connecting client previously would run into a \ 
TCP connection timeout.

Now a more specific error will be returned to the client before connection closure.

Contributed by @SimonUnge (AWS).

CLI Tools

Bug Fixes

rabbitmqctl add_vhosts failed with an exception when --default-queue-type option \ 
was provided.

Management Plugin

Bug Fixes

HTTP API endpoint PUT /api/vhosts/{name} incorrectly used defaultqueuetype for \ 
default queue type
key name. It is now default_queue_type, the same key as returned by GET \ 
/api/vhosts/{name}.

HTTP API will now respond with a 405 Method Not Allowed instead of a 500 when
an unsupported method is used by the client.

Contributed by @gomoripeti (CloudAMQP).

AMQP 1.0 Plugin

Bug Fixes

Fixed AMQP 1.0 authentication issue that affected OAuth 2 token users.