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

RabbitMQ `3.7.15` is a maintenance release. It focuses on bug fixes and minor usability improvements. This release or later. It is also the first release to support Erlang 22. Per the new Erlang version support policy in effect starting with January 2019, this release . Make sure a is used before upgrading. explains what package repositories and tools can be used to provision latest patch versions of Erlang `20.3.x` and `21.x`. This release requires Erlang/OTP 20.3 or later. When upgrading to this release and upgrading Erlang to 21.x at the same time, extra care has to be taken. Since CLI tools from RabbitMQ releases older than 3.7.7 will fail on Erlang 21, RabbitMQ must be upgraded before Erlang. See upgrade and compatibility notes if upgrading from an earlier release. See the for general documentation on upgrades and for release notes of other releases. Any questions about this release, upgrades or RabbitMQ in general are welcome on the . `rabbitmq.conf` validation errors on startup unintentionally lacked a lot of relevant details. Contributed by Grigory Starinkin. GitHub issue: Message store compaction could enter a race condition with queue operations. GitHub issue: Internal schema data store consistency checks used an on-disk location which could be unintentionally preserved between deployments and make subsequent deployments fail. Now an entirely in-memory set of tables is used for schema consistency checks. GitHub issue: When had to send both positive and negative acknowledgements around the same time, it could be done in a way that would violate expectations of most client libraries. GitHub issue: Policy validation could allow invalid values in certain cases. GitHub issue: `amq.rabbitmq.log` exchage was lazily initialised and could be temporarily unavailable after node start. GitHub issue: Clearing a policy with `overflow` behaviour or removing the key from it did not roll back the overflow behaviour to `drop-head` (the default). GitHub issue: Missing `getconf` command (used to fetch platform's memory page size) is now handled more gracefully with a default value. GitHub issue: Initial Erlang 22 compatibility. GitHub issues: , , Connection tracking is now more efficient, reducing node load and internal event backlog in case of . GitHub issues: , Enabled kernel sendfile for HTTP API documentation pages could lead to leaked file descriptors when those pages are accessed repeatedly

a tab is always open for weeks and weeks). The plugin now disables sendfile for those static files by default. It can be manually enabled via configuration as needed. GitHub issue: Listing permissions could result in a 500 response. GitHub issue: When CORS headers were enabled, binding endpoints were inaccessible due to an exception. GitHub issue: An option to display message rates for the last 8 and 24 hours was hidden in the UI even when data for those time intervals was available. GitHub issue: Information unit suffix incorrectly suggested that values were powers of 10 (gigabyte) instead of power of 2 (gibibyte). GitHub issue: Default host specified in `amqp10.defaultvhost` (`rabbitmqamqp10.default_vhost` in classic config format) now takes precedence over `defaultvhost` (`rabbit.defaultvhost`) in the core broker. GitHub issue: Connections to source and destination nodes are now correctly closed if topology operations fail on either end (e.g. due to insufficient permissions). Contributed by Grigory Starinkin. GitHub issue: Improved handling of cases where AMQP 1.0 endpoint connection was refused access to a virtual host. GitHub issue: The plugin now provides a new CLI command and HTTP API endpoint for restarting a dynamic Shovel. GitHub issue: Queue federation now uses a more informative consumer tag value. GitHub issue: Streamling `list_` commands could hang when encountering an error from one of the cluster nodes. GitHub issue: `rabbitmqctl delete_queue -u` failed argument validation due to a typo. GitHub issue: `rabbitmq-diagnostics cipher_suites` now provides a way to display all available (not just enabled) cipher suites. GitHub issue: When an unsupported node name is used, CLI tools will now produce more specific error messages. GitHub issue: `rabbitmq-diagnostics erlang_version` now supports `--offline`. GitHub issue: Default STOMP plugin log is now used for `CONNECT` frames without credentials. Contributed by Nick Goossens. GitHub issue: Direct connections (via Erlang distribution) from outside of a RabbitMQ should no longer fail due to a dependency on a module that was previously a part of core RabbitMQ broker. GitHub issue: Virtual host endpoint requests were not cached. GitHub issues: , Calculation worker process could fail due to an exception. GitHub issue: `LIKE` operator could be incorrectly evaluated. GitHub issue: Warning: The source code archive provided by GitHub only contains the source of the broker, not the plugins or the client libraries. Please download the archive named `rabbitmq-server-3.7.15.tar.xz`.