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

RabbitMQ `3.7.16` is a maintenance release. It focuses on bug fixes and minor usability improvements. 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 `21.3.x` and `22.x`. OpenSUSE Leap 42.3 has , 2019. Packages for that distribution are therefore no longer produced because upstream OpenSUSE repositories are no longer available. When upgrading to this release and upgrading Erlang to 21.x or later 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 or later, RabbitMQ must be upgraded before Erlang. See upgrade and compatibility notes first 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 . When a node hosting an exclusive queue was restarted with queue leader locator being something other than "node local", redeclaration of the queue failed. Contributed by Lajos Gerecs. GitHub issue: It is now possible to configure default worker pool size: ``` ini defaultworkerpool_size = 1024 ``` This may be necessary in environments with a large number of queues (say, hundreds of thousands) to speed up queue and binding recovery on node boot. By default the size of the pool is computed as the number of . GitHub issue: `rabbitmqctl report` and `rabbitmqctl listqueues` could fail with a `{badargument,type}` because of a 3.8-specific column was erroneously listed as supported. Contributed by Lajos Gerecs. GitHub issue: New health check: `rabbitmq-diagnostics checkvirtualhosts`. New observability command, `rabbitmq-diagnostics log_location [--all]`, displays log file location(s) on target node. The node is assumed to be running. GitHub issue: New observability commands, `rabbitmq-diagnostics logtail` and `rabbitmq-diagnostics logtail_stream`, provide a way to remotely inspect recent log file entries on a running node. The commands are meant to be used for troubleshooting and not to automate log aggregation. GitHub issue: `rabbitmq-diagnostics schema_info` displays information about internal database schema (tables, their properties and metadata). When multiple definition files were , errors were not reported the same way they would be with a single file. GitHub issue: The plugin now disables for the definition import endpoints and reports progress using periodic so that the connection is kept alive even if importing definition takes a long time. GitHub issue: `3.7.15` introduced a regression where Shovels would not try to reconnect after a network failure. GitHub issue: Default maximum connection limit set by a dependency (1024) has been lifted. GitHub issue: Client ID wasn't propagated to connection metadata for MQTT connections over WebSockets. GitHub issue: Default maximum connection limit set by a dependency (1024) has been lifted. GitHub issue: It is now possiible to configure HTTPS proxy settings for the HTTPS backend. GitHub issue: Exit code 69 is now considered a success again in the systemd service file. GitHub issues: , 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.16.tar.xz`.