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

RabbitMQ `3.7.5` a maintenance release that primarily includes bug fixes. This release includes one potential incompatibility with earlier `3.7.x` releases. It will only affect applications that use a lot (at least hundreds) of channels per connection. Previous behavior can be restored via configuration. See upgrade and compatibility notes if upgrading from an earlier release. See the for general documentation on upgrades. See for release notes of other releases. Topic authorisation check could fail with an exception. GitHub issue: Some runtime parameters and operator policies were rejected during definition import. GitHub issue: , Queues could run into an exception under memory pressure. GitHub issue: During parallel cluster formation nodes could run into an exception when inserting seed data (default virtual host, user and permissions). GitHub issue: New `ha-promote-on-failure` queue mirroring setting to augment already existing `ha-promote-on-shutdown`. GitHub issue: `queue.delete` operations will now force delete queues that don't have a [promotable master](https://www.rabbitmq.com/ha.html#unsynchronised-mirrors). GitHub issue: Lock contention in internal database is now much lower when a node with a lot of exclusive queues shuts down or is otherwise considered to be unavailable by peers. This means fewer CPU cycles spent cleaning up the exclusive queues. GitHub issue: Default (a.k.a. `channel_max`) has been lowered from `65535` to `2047`. The new default is much safer and will reduce the effect application channel leaks have on node resource consumption. This is a potentially breaking change. Systems where a lot (at least hundreds) of channels per connection are used should explicitly override `channel_max` in the to a higher suitable value, e.g.: ``` channel_max = 4000 ``` GitHub issue: dependency has been updated to `1.5.x` which should prevent rare cases of mass termination of client connections. `-t` (`--timeout`) is now only displayed for commands that will actually use it. GitHub issue: `GET /api/overview` could fail if SNI for management plugin listener was configured. GitHub issue: `rabbitmqadmin` could run into an exception with certain formatting settings on Python 2.x. GitHub issue: HTTP API stats documentation used incorrect field names. GitHub issue: LDAP server-initiated connection closure was not handled gracefully by connection pool. Kudos to Adam Gardner for investigating this issue. GitHub issues: , `authldap.idletimeout` now defaults to 300 seconds instead of `infinity`. GitHub issue: `grouplookupbase` was not configurable via the new style config format. GitHub issue: `authldap.log` didn't accept `networkunsafe` for severity value. GitHub issue: It is now possible to configure TLS options for LDAP server connections via the . GitHub issue: Federation upstream sets could run into a type error with exchange federation. GitHub issue: Valid dynamic Shovel properties can be rejected by validation. GitHub issue: Shovel names are again included into (application-provided) connection names and can therefore be seen in the management UI. GitHub issue: China-based AWS regions now use a correct base API URI. GitHub issue: The plugin could fail to discover all nodes in a returned instance set. GitHub issue: The plugin now supports with much lower default values since RSD is for stateful set deployments. GitHub issue: It wasn't possible to send some messages using QPid JMS client over AMQP 1.0. GitHub issue: New style config format was not interpreting IP addresses correctly. GitHub issue: It wasn't possible to configure TCP listener(s) in the new style config format. 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.5.tar.gz`.