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

RabbitMQ `3.13.1` is a maintenance release in the `3.13.x` . Starting June 1st, 2024, community support for this series will only be provided to and those who hold a valid . Please refer to the upgrade section from the if upgrading from a version prior to 3.13.0. This release requires Erlang 26 and supports Erlang versions up to `26.2.x`. has more details on Erlang version requirements for RabbitMQ. As of 3.13.0, RabbitMQ requires Erlang 26. Nodes will fail to start on older Erlang releases. Users upgrading from 3.12.x (or older releases) on Erlang 25 to 3.13.x on Erlang 26 (both RabbitMQ and Erlang are upgraded at the same time) must consult the and first. Release notes can be found on GitHub at . Classic queue v2 message store compaction could fail behind under high enough load, significantly increasing node's disk space footprint. GitHub issues: , Improved quorum queue safety in mixed version clusters. GitHub issue: When Khepri was enabled and virtual host recovery failed, subsequent recovery attempts also failed. GitHub issue: Messages published without any headers set on them did not have a header property set on them. This change compared to 3.12.x was not intentional. GitHub issues: , Free disk space monitor on Windows ran into an exception if external call to `win32sysinfo.exe` timed out. GitHub issue: `channelmaxper_node` is a new per-node limit that allows to put a cap on the number of AMQP 0-9-1 channels that can be concurrently open by all clients connected to a node: ``` ini channelmaxper_node = 5000 ``` This is a guardrail mean to protect nodes from . Contributed by @illotum (AWS). GitHub issue: Avoids a Windows-specific stream log corruption that affected some deployments. GitHub issue: When a cannot be created because of a duplicate partition name, a more informative error message is now used. GitHub issue: `rabbitmq-plugins list --formatter=json --silent` will no longer emit any warnings when some of the plugins in the are missing. Contributed by @Ayanda-D. GitHub issue: Configuring a JWKS URL without specifying a CA certificate resulted in an exception with Erlang 26's TLS implementation. GitHub issue: Set default `sort` query parameter value for better compatibility with an external Prometheus scraper. Note that the is the recommended way of RabbitMQ using Prometheus-compatible tools. GitHub issue: When a tab (Connections, Queues and Streams, etc) is switched, a table configuration pane from the previously selected tab is now hidden. Contributed by @ackepenek. GitHub issue: `GET /api/queues/{vhost}/{name}` now supports `enablequeuetotals` as well as `disable_stats`. This combination of query parameters can be used to retrieve message counters while greatly reducing the number of metrics returned by the endpoints. Contributed by @aaron-seo (AWS). GitHub issue: Exchange federation now can be configured to use a custom queue type for their internal buffers. To use a quorum queue, set the `queue-type` federation policy key to `quorum`. GitHub issues: , `rabbitmqfederationrunninglinkcount` is a new metric provided via Prometheus. GitHub issue: `osiris` was updated to `khepri` was upgraded to `cowboy` was updated to To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.13.1.tar.xz` instead of the source tarball produced by GitHub.