release-notes/3.8.17.md
RabbitMQ 3.8.17 is a maintenance release that includes a security patch.
This release addresses an undisclosed vulnerability with CVSS 3.1 score of 3.1 (low): CVE-2021-32718.
Our team would like to thank Christian Rellmann from usd AG for responsibly disclosing the vulnerability and helping us verify a fix.
RabbitMQ releases are distributed via GitHub, Cloudsmith, and PackageCloud.
This release requires Erlang 23.2 and supports Erlang 24.
Provisioning Latest Erlang Releases explains what package repositories and tools can be used to provision modern Erlang versions.
See the Upgrading guide for general documentation on upgrades and RabbitMQ change log for release notes of other releases.
If upgrading from a3.7.x release, see 3.8.0 release notes
upgrade and compatibility notes first.
If upgrading from a 3.6.x or older release series, first upgrade
to 3.7.27 and then to this version.
Any questions about this release, upgrades or RabbitMQ in general are welcome on the RabbitMQ mailing list and RabbitMQ community Slack.
Queue index efficiency improvements, mostly around peak memory consumption with large backlogs of small messages.
Note that some of the improvements come from more optimal defaults: those will only be applicable to newly created virtual hosts (or new clusters).
Consumer delivery acknowledgement timeout default has been bumped to 30 minutes (previously 15 minutes). The value can be overridden.
GitHub issue: #3033
A classic queue with single active consumer option enabled could run into an exception after a restart or initial enablement of the management plugin.
GitHub issue: #3072
A combination of HTTPS (TLS) settings and advanced HTTP server settings resulted in an exception.
GitHub issue: #3039
External stats collector is now restarted again if it fails for any reason.
Contributed by @luos.
GitHub issue: #3040
When nodes are restarted, schema database tables used by this plugin are now reconciled with cluster peers the same way RabbitMQ core does it.
GitHub issue: #3067
When nodes are restarted, schema database tables used by this plugin are now reconciled with cluster peers the same way RabbitMQ core does it.
GitHub issue: #3067
When nodes are restarted, schema database tables used by this plugin are now reconciled with cluster peers the same way RabbitMQ core does it.
Contributed by @mwfriedm.
GitHub issue: rabbitmq/rabbitmq-delayed-message-exchange#163
When nodes are restarted, schema database tables used by this plugin are now reconciled with cluster peers the same way RabbitMQ core does it.
GitHub issue: rabbitmq/rabbitmq-lvc-exchange#28
MQTT-over-WebSockets client connections were not accounted for by the file handle tracking mechanism (metric and resource alarm).
GitHub issue: #3076
None in this release.
To obtain source code of the entire distribution, please download the archive named rabbitmq-server-3.8.17.tar.xz
instead of the source tarball produced by GitHub.