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

RabbitMQ `3.7.13` is a maintenance release. It focuses on bug fixes and minor usability improvements. This release or later. 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 . Binding and unbinding operations could fail with a `NOT_FOUND` channel exception if binding tables got out of sync. GitHub issues: , , Eliminated an accumulating inefficiency around topic-based authorisation (only topic exchanges are affected). Contributed by . GitHub issue: TCP connections could accumulate when was enabled and proxy's TCP connections were closed before Proxy protocol header was received and parsed. GitHub issue: When a queue was deleted, about consumer cancellation (`consumer.deleted`) were not emitted. GitHub issue: Connection tracking subsystem failed and logged an exception when connection was closed before it could be registered. GitHub issue: Exclusive queue property mismatch during queue declaration now produces a more helpful error message. GitHub issue: Erlang 22 forward compatibility: support more cipher suites for config value encryption. GitHub issue: `rabbitmqctl shutdown` in `--wait` mode now uses node names instead of `gethostname(2)` when inferring if target node is remote. This is more reliable as it takes explicitly set node names and `ERL_INETRC` settings into account. In addition, it treats all nodes that have `@localhost` in the name as local (running on the same host). GitHub issue: . `rabbitmqctl forgetclusternode` produces a more helpful error message when asked to remove a node with running RabbitMQ application. GitHub issue: New command, `rabbitmqctl force_gc`, that requests fullsweep GC for all processes on the target node. GitHub issue: All RabbitMQ CLI tools now support `--version` as well as `version` as a command. GitHub issue: `rabbitmqadmin`'s' `declare vhostlimit` and `delete vhostlimit` did not support the vhost parameter. GitHub issue: `PUT /api/vhost-limits/{vhost}/{limit}` documentation was incorrect and used confusing language. GitHub issue: Debian and RPM packages no longer source `/etc/profile` in post installation scripts. GitHub issue: Federation links could fail to start with an `{error, already_started} `. GitHub issue: AMQP 1.0 endpoint URIs could fail to parse. GitHub issue: User tags are now passed to virtual host, resource and topic authorisation check endpoints as a space-separated string. Contributed by . GitHub issue: HTTP provider did not correctly update `If-Modified-Since` request header when certificates (and thus their `Last-Modified` response header) were updated. 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-3.7.13.tar.gz`.