RabbitMQ 3.7.3-rc.2

RabbitMQ 3.7.3 RC2

RabbitMQ 3.7.3 RC2 is a maintenance release candidate.

Upgrades and Compatibility

This release has no known incompatibilities with earlier 3.7.x versions.
See 3.7.0 release notes upgrade and compatibility notes if upgrading from an earlier release.

See the Upgrading guide for general documentation on upgrades.

See RabbitMQ change log for release notes of other releases.

Changes

Core Server

Bug Fixes

• Logging to amq.rabbitmq.log exchange is available again as a logging mechanism. Note that
  the user must opt-in by setting log.exchange = true in the config file.

  GitHub issue: rabbitmq-server#1456

• During node boot, the logger will temporarily accept a much higher maximum rate so that no messages are dropped.

  GitHub issue: rabbitmq-server#1471

• Plugin activation could hang if a plugin's channel interceptor failed to activate with an exception.

  GitHub issue: rabbitmq-server#1477

• During node boot, virtual host that are not yet initialised could be queried for status, which
  resulted in log noise.

  GitHub issue: rabbitmq-server#1472

Enhancements

• Internal authN backend will now prohibit logins with a blank passwords. Such attempts
  are usually made by mistake because a passwordless user that was meant to authenticate
  using x509 (TLS) certificates was not configured to use the correct authentication
  mechanism.

  Note that the same behavior can already be achieved using a credential validator, so this is
  just an extra safety measure.

  GitHub issue: rabbitmq-server#1465

Management Plugin

Bug Fixes

• Definition import now stores global parameters in a way that the MQTT plugin expects.

  GitHub issue: rabbitmq-management#528

• User update form now successfully updates tags for passwordless users (or if the password is cleared at the same time).

  GitHub issue: rabbitmq-management#533

Enhancements

• Requeue is now the default option in the Get Messages section.

  Contributed by @dparkinson.

  GitHub issue: rabbitmq-management#542

• For passwordless users, the "no password" option on the user editing form is now preselected.

  GitHub issue: rabbitmq-management#537

LDAP AuthN/AuthZ Backend Plugin

Bug Fixes

• More config keys are now supported via new style config format.

  GitHub issue: rabbitmq-auth-backend-ldap#78

Peer Discovery Consul Plugin

• When a node registers with Consul it will now set its initial health check status to passing.
  Previously the node would be in the critical state until it first reported its health for the
  first time (in 15 seconds with default settings), which could prevent its peers from discovering it.

  Kudos to @andersenleo for investigating this issue and recommending a solution.

  GitHub issue: rabbitmq-peer-discovery-consul#8

CLI Tools

Bug Fixes

• CLI tools honor RABBITMQ_CTL_ERL_ARGS again.

  GitHub issue: rabbitmq-server#1461

Source code archives

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.3.tar.gz.

RabbitMQ 3.7.3-rc.1

RabbitMQ 3.7.3 RC1

RabbitMQ 3.7.3 RC1 is a maintenance release candidate.

Upgrades and Compatibility

This release has no known incompatibilities with earlier 3.7.x versions.
See 3.7.0 release notes upgrade and compatibility notes if upgrading from an earlier release.

See the Upgrading guide for general documentation on upgrades.

See RabbitMQ change log for release notes of other releases.

Changes

Core Server

Bug Fixes

• Logging to amq.rabbitmq.log exchange is available again as a logging mechanism. Note that
  the user must opt-in by setting log.exchange = true in the config file.

  GitHub issue: rabbitmq-server#1456

• During node boot, the logger will temporarily accept a much higher maximum rate so that no messages are dropped.

  GitHub issue: rabbitmq-server#1471

Enhancements

• Internal authN backend will now prohibit logins with a blank passwords. Such attempts
  are usually made by mistake because a passwordless user that was meant to authenticate
  using x509 (TLS) certificates was not configured to use the correct authentication
  mechanism.

  Note that the same behavior can already be achieved using a credential validator, so this is
  just an extra safety measure.

  GitHub issue: rabbitmq-server#1465

Management Plugin

Bug Fixes

• Definition import now stores global parameters in a way that the MQTT plugin expects.

  GitHub issue: rabbitmq-management#528

• User update form now successfully updates tags for passwordless users (or if the password is cleared at the same time).

  GitHub issue: rabbitmq-management#533

Enhancements

• For passwordless users, the "no password" option on the user editing form is now preselected.

  GitHub issue: rabbitmq-management#537

LDAP AuthN/AuthZ Backend Plugin

Bug Fixes

• More config keys are now supported via new style config format.

  GitHub issue: rabbitmq-auth-backend-ldap#78

CLI Tools

Bug Fixes

• CLI tools honor RABBITMQ_CTL_ERL_ARGS again.

  GitHub issue: rabbitmq-server#1461

Source code archives

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.3.tar.gz.

RabbitMQ 3.6.15

RabbitMQ 3.6.15

RabbitMQ 3.6.15 is a maintenance release.

Upgrades and Compatibility

See the "Upgrading clusters" section of the
documentation for general documentation on upgrades.

This release has no known incompatibilities with versions 3.6.7 through
3.6.14. See the upgrade and compatibility sections in the 3.6.7 release
notes
if upgrading from an earlier release.

3.6.x Series Support Timeline

Please read this node on RabbitMQ 3.6.x series support
timeline.

Core Server

Bug Fixes

• Avoid infinite loop when dropping entries in the GM.

  GitHub issue: rabbitmq-server#1431

• Various changes to the OCF scripts.

  Github issues: rabbitmq-server-release#66,
  rabbitmq-server-release#67,
  rabbitmq-server-release#73

Enhancements

• Internal authN backend will now prohibit logins with a blank passwords. Such attempts
  are usually made by mistake because a passwordless user that was meant to authenticate
  using x509 (TLS) certificates was not configured to use the correct authentication
  mechanism.

  Note that the same behavior can already be achieved using a credential validator,
  so this is just an extra safety measure.

  Github issue: rabbitmq-server#1466

Management Plugin

Bug Fixes

• Multi-input forms (such as message properties) again submit all fields.

  GitHub issues: rabbitmq-management#511

• User update form now successfully updates tags for passwordless users (or if the password is cleared at the same time).

  GitHub issue: rabbitmq-management#533

• Content-Type header was returned twice in API responses.

  GitHub issue: rabbitmq-management#527

• Avoid duplicated event handlers in the UI.

  Github issue: rabbitmq-management#516

• Use auto width to make option values fully visible.

  Github issue: rabbitmq-management#519

MQTT Plugin

Bug Fixes

• Concurrently registering consumers could fail with a "Key exists" exception in the log.

  GitHub issue: rabbitmq-mqtt#132

Federation Plugin

Bug Fixes

• Disabling policy (or plugin) now cleans up all internal exchanges and queues used by federation links.

  GitHub issue: rabbitmq-federation#63

Standalone MacOS Package

Bug Fixes

• Standalone MacOS package now ships with Erlang/OTP 20.1 which is compatible with High Sierra.

  GitHub issue: rabbitmq-server-release#68

Debian Package

Bug Fixes

• Make adm the group owner for RabbitMQ log directories.

  GitHub issue: rabbitmq-server-release#70

Web MQTT Plugin

Bug Fixes

• https/web-mqtt listener displayed incorrect port in management UI.

  GitHub issue: rabbitmq-web-mqtt#25

Top Plugin

Bug Fixes

• Fix node and row selectors after jQuery upgrade to 1.12.

  GitHub issue: rabbitmq-top#29

Erlang Client

Buf Fixes

• Enable hostname verification for OTP 19.

  Github issue: rabbitmq-erlang-client#95

Upgrading

To upgrade a non-clustered RabbitMQ simply install the new version. All
configuration and persistent message data are retained. When upgrading
using definitions export/import from versions earlier than 3.6.0, see
http://rabbitmq.com/passwords.html.

To upgrade a RabbitMQ cluster, follow the instructions in RabbitMQ
documentation.

Source code archives

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.6.15.tar.xz.

RabbitMQ 3.6.15-rc.1

RabbitMQ 3.6.15 RC1

RabbitMQ 3.6.15 RC1 is a candidate of a maintenance release.

Upgrades and Compatibility

See the "Upgrading clusters" section of the
documentation for general documentation on upgrades.

This release has no known incompatibilities with versions 3.6.7 through
3.6.14. See the upgrade and compatibility sections in the 3.6.7 release
notes
if upgrading from an earlier release.

3.6.x Series Support Timeline

Please read this node on RabbitMQ 3.6.x series support
timeline.

Core Server

Bug Fixes

• Avoid infinite loop when dropping entries in the GM.

  GitHub issue: rabbitmq-server#1431

• Various changes to the OCF scripts.

  Github issues: rabbitmq-server-release#66,
  rabbitmq-server-release#67,
  rabbitmq-server-release#73

Management Plugin

Bug Fixes

• Multi-input forms (such as message properties) again submit all fields.

  GitHub issues: rabbitmq-management#511

• Content-Type header was returned twice in API responses.

  GitHub issue: rabbitmq-management#527

• Avoid duplicated event handlers in the UI.

  Github issue: rabbitmq-management#516

• Use auto width to make option values fully visible.

  Github issue: rabbitmq-management#519

MQTT Plugin

Bug Fixes

• Concurrently registering consumers could fail with a "Key exists" exception in the log.

  GitHub issue: rabbitmq-mqtt#132

Federation Plugin

Bug Fixes

• Disabling policy (or plugin) now cleans up all internal exchanges and queues used by federation links.

  GitHub issue: rabbitmq-federation#63

Standalone MacOS Package

Bug Fixes

• Standalone MacOS package now ships with Erlang/OTP 20.1 which is compatible with High Sierra.

  GitHub issue: rabbitmq-server-release#68

Debian Package

Bug Fixes

• Make adm the group owner for RabbitMQ log directories.

  GitHub issue: rabbitmq-server-release#70

Web MQTT Plugin

Bug Fixes

• https/web-mqtt listener displayed incorrect port in management UI.

  GitHub issue: rabbitmq-web-mqtt#25

Top Plugin

Bug Fixes

• Fix node and row selectors after jQuery upgrade to 1.12.

  GitHub issue: rabbitmq-top#29

Erlang Client

Buf Fixes

• Enable hostname verification for OTP 19.

  Github issue: rabbitmq-erlang-client#95

Upgrading

To upgrade a non-clustered RabbitMQ simply install the new version. All
configuration and persistent message data are retained. When upgrading
using definitions export/import from versions earlier than 3.6.0, see
http://rabbitmq.com/passwords.html.

To upgrade a RabbitMQ cluster, follow the instructions in RabbitMQ
documentation.

Source code archives

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.6.15.tar.xz.

RabbitMQ 3.7.2

RabbitMQ 3.7.2

RabbitMQ 3.7.2 fixes an issue in the HTTP auth backend plugin that was introduced in 3.7.1.
It has no other functional changes compared to 3.7.1.

Upgrades and Compatibility

This release has no known incompatibilities with earlier 3.7.x versions.
See 3.7.0 release notes upgrade and compatibility notes if upgrading from an earlier release.

See the Upgrading guide for general documentation on upgrades.

See RabbitMQ change log for release notes of other releases.

Changes

Auth Backend HTTP Plugin

Bug Fixes

• Plugin threw an exception while performing HTTP requests.

  GitHub issue: rabbitmq/rabbitmq-auth-backend-http#62

Source code archives

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.2.tar.gz.

RabbitMQ 3.7.1

RabbitMQ 3.7.1

RabbitMQ 3.7.1 is a bug fix release.

Upgrades and Compatibility

This release has no known incompatibilities with 3.7.0. See 3.7.0 release notes
upgrade and compatibility notes if upgrading from an earlier release.

See the Upgrading guide
for general documentation on upgrades.

See RabbitMQ change log for release notes of other releases.

Changes

Core Server

Bug Fixes

• Standalone Mac build now bundles a version of Erlang/OTP that is compatible with High Sierra (20.1, to be specific).

  GitHub issue: rabbitmq/rabbitmq-server-release#68

• RabbitMQ distribution now again can be built in an offline environment (one without access to the Internet).

  GitHub issue: rabbitmq/rabbitmq-server-release#61

• total_memory_available_override_value was not available via the new config format.

  GitHub issue: rabbitmq/rabbitmq-server#1445

CLI Tools

Bug Fixes

• rabbitmqctl set_parameter ignored the virtual host argument and default to the default (/) vhost.

  GitHub issue: rabbitmq/rabbitmq-cli#232

AWS Peer Discovery Plugin

Bug Fixes

• HTTP client proxy settings were applied to late and thus didn't have any effect.

  GitHub issue: rabbitmq/rabbitmq-peer-discovery-common#5

Consul Peer Discovery Plugin

Bug Fixes

• HTTP client proxy settings were applied to late and thus didn't have any effect.

  GitHub issue: rabbitmq/rabbitmq-peer-discovery-common#5

etcd Peer Discovery Plugin

Bug Fixes

• HTTP client proxy settings were applied to late and thus didn't have any effect.

  GitHub issue: rabbitmq/rabbitmq-peer-discovery-common#5

Kubernetes Peer Discovery Plugin

Bug Fixes

• HTTP client proxy settings were applied to late and thus didn't have any effect.

  GitHub issue: rabbitmq/rabbitmq-peer-discovery-common#5

Management and Management Agent Plugins

Bug Fixes

• Certain node metrics in multi-cluster environment were not merged correctly
  when aggregated.

  GitHub issue: rabbitmq/rabbitmq-management#525

Auth Backend HTTP Plugin

Bug Fixes

• It was not possible to configure request HTTP method using the new style config file.

  GitHub issue: rabbitmq/rabbitmq-auth-backend-http#61

Shovel Management Plugin

Bug Fixes

• Move Messages form on individual queue page didn't provide all the Shovel parameters required as
  of 3.7.0 and thus did not transfer any messages.

  GitHub issue: rabbitmq/rabbitmq-shovel-management#24

Erlang AMQP 1.0 Client

Bug Fixes

• Continuation frames without delivery_id were not handled correctly.

  GitHub issue: rabbitmq/rabbitmq-amqp1.0-client#11

Source code archives

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.1.tar.gz.

RabbitMQ 3.7.0

This release introduces new features, changes to RabbitMQ distribution (e.g. what plugins ship
with it), and bug fixes. It also includes all the changes from the 3.6.x release series unless stated otherwise.

Documentation for this release is available at the RabbitMQ website.

Breaking Changes

• Minimum required Erlang/OTP version is now 19.3. Recent Erlang versions can be obtained from Erlang Solutions, RabbitMQ zero dependency Erlang RPM, as well as main and backports repositories of recent Ubuntu and Debian releases.

  GitHub issues: rabbitmq-server#1305, rabbitmq-server#1307, rabbitmq-common#234.

• HTTP API has minor breaking changes in several endpoints (see below).

• .NET client is now .NET Core-compatible.
  Starting with 3.7.0, .NET client releases are decoupled from RabbitMQ server releases and exclusively distributed via the RabbitMQ.Client NuGet package.

• Starting with 3.7.0, Java client releases are decoupled from RabbitMQ server releases and exclusively distributed via Maven: RabbitMQ Milestones Maven repository, RabbitMQ Maven repository, as well as Maven Central.

• Users tagged with administrator now implicitly have access to most operations in all vhosts,
  including those they don't have explicit permissions for.

  GitHub issue: rabbitmq-management#461

• Plugins now must depend on the rabbit application in order to be recognised as such by rabbitmq-plugins list.
  Plugins that do not have the dependency will still function, can be enabled or disabled but won't appear
  in rabbitmq-plugins list output.

• rabbitmq_management_visualiser plugin no longer ships with RabbitMQ and is considered to be deprecated. Installations that have this plugin enabled must disable it before upgrading. This can
  be done using rabbitmq-plugins disable (which supports offline modifications)
  or by updating the list of plugins in RABBITMQ_ENABLED_PLUGINS_FILE.

Erlang/OTP 20 Support

Erlang/OTP 20 has breaking changes that affected RabbitMQ.

3.7.0 supports OTP 20, including upgrades of existing installations to OTP 20. This required changes to the core and multiple plugins that ship with RabbitMQ.

GitHub issues: rabbitmq-server#1243, rabbitmq-server#1250, rabbitmq-server#1268,
rabbitmq-server#1272, rabbitmq-federation#58, rabbitmq-management-agent#47,
rabbitmq-management#415, rabbitmq-stomp#115

Core Server

Enhancements

• New configuration file format

  RabbitMQ now supports a new configuration file format.
  The format is based on sysctl
  and is similar to .ini files. Erlang term configuration files are still supported, it is also
  possible to combine the two formats (use both rabbitmq.conf and advanced.config).

  Most documentation examples were updated to use both new and classic config formats. See the docs
  at next.rabbitmq.com, in particular the configuration guide,
  for more information.

  GitHub issues: rabbitmq-server#550,
  rabbitmq-server#1103,
  rabbitmq-auth-backend-ldap#59

• Pluggable cluster peer discovery

  Automatic clustering for blank (without an existing database) nodes now can discover
  peers using pluggable backends. This is a set of features adopted from the rabbitmq-autocluster plugin by Gavin Roy.
  Two implementations are available out of the box: one uses a config file- and another DNS A records.
  Several more are available via plugins:

  • AWS
  • Consul
  • etcd
  • Kubernetes

  GitHub issues: rabbitmq-server#486, rabbitmq-server#988, rabbitmq-server#1143
  rabbitmq-server#1202, rabbitmq-server#1171, rabbitmq-server#1257, rabbitmq-server#1247

• Nodes in a cluster now can be restared in arbitrary order. They will attempt to contact
  one of the previously seen peers periodically (10 times with 30 second intervals by default).

  GitHub issue: rabbitmq-server#1022,
  rabbitmq-server#487

• Every virtual host now has separate message stores.
  This improves resiliency and reduces contention in multitenant environments,
  plus makes development of tools that perform backups and recovery of resting data easier
  in the future.

  During the upgrade nodes will migrate data to this new layout. This can take some time.
  To reduce the amount of time, drain as many queues as possible before upgrading, e.g.
  by stopping publishers without stopping consumers for a period of time.

  GitHub issues: rabbitmq-server#567, rabbitmq-server#1146, rabbitmq-server#1280,
  rabbitmq-management#446, rabbitmq-server#1303, rabbitmq-management#460, rabbitmq-server#1321

• New LevelDB-based message store index plugin.

  GitHub issue: rabbitmq-server#838

• Support config file path values with and without file extensions

  RabbitMQ no longer requires RABBITMQ_CONFIG_FILE values to not have a .config or .conf suffix. It will try appending both suffixes as needed when searching for suitable config file(s) to load.

  Github Issue: rabbitmq-server#691

• Operators now can configure how many concurrent connections are allowed in a vhost.

  GitHub issue: rabbitmq-server#500

• Operators now can configure how many queues can exist in a vhost.

  GitHub issue: rabbitmq-server#501

• Operator policies: their definitions are merged with the standard (user) policies and allow operators put global
  limits in place, e.g. max queue length or message TTL.

  GitHub issue: rabbitmq-server#930

• It is now possible to configure a limited prefetch value for all newly opened channels by default.
  This helps prevent consumers that never acknowledge deliveries from exhausting server resources.
  It is important to make sure that consumers that use manual acknowledgements can cope with this
  change before enabling it.

  GitHub issue: rabbitmq-server#1367

• Plugin version constraints

  RabbitMQ now has a mechanism for plugin authors to indicate what versions a plugin is compatible with.
  Incompatible plugins are logged and ignored.

  Github issues: rabbitmq-server#591, rabbitmq-server#735, [rabbi...

RabbitMQ 3.7.0-rc.2

Release Highlights

These are release notes for RabbitMQ 3.7.0 RC2, a candidate of a feature release.

This release introduces new features, changes to RabbitMQ distribution (e.g. what plugins ship
with it), and bug fixes. It also includes all the changes from the 3.6.x release series unless stated otherwise.

Documentation for this preview is available at next.rabbitmq.com.

Breaking Changes

• Minimum required Erlang/OTP version is now 19.3. Recent Erlang versions can be obtained from Erlang Solutions, RabbitMQ zero dependency Erlang RPM, as well as main and backports repositories of recent Ubuntu and Debian releases.

  GitHub issues: rabbitmq-server#1305, rabbitmq-server#1307, rabbitmq-common#234.

• HTTP API has minor breaking changes in several endpoints (see below).

• .NET client is now .NET Core-compatible.
  Starting with 3.7.0, .NET client releases are decoupled from RabbitMQ server releases and exclusively distributed via the RabbitMQ.Client NuGet package.

• Starting with 3.7.0, Java client releases are decoupled from RabbitMQ server releases and exclusively distributed via Maven: RabbitMQ Milestones Maven repository, RabbitMQ Maven repository, as well as Maven Central.

• Users tagged with administrator now implicitly have access to most operations in all vhosts,
  including those they don't have explicit permissions for.

  GitHub issue: rabbitmq-management#461

• Plugins now must depend on the rabbit application in order to be recognised as such by rabbitmq-plugins list.
  Plugins that do not have the dependency will still function, can be enabled or disabled but won't appear
  in rabbitmq-plugins list output.

• rabbitmq_management_visualiser plugin no longer ships with RabbitMQ and is considered to be deprecated.

Erlang/OTP 20 Support

Erlang/OTP 20 has breaking changes that affected RabbitMQ.

3.7.0 supports OTP 20, including upgrades of existing installations to OTP 20.
This required changes to the core and multiple plugins that ship with RabbitMQ.

GitHub issues: rabbitmq-server#1243, rabbitmq-server#1250, rabbitmq-server#1268,
rabbitmq-server#1272, rabbitmq-federation#58, rabbitmq-management-agent#47,
rabbitmq-management#415, rabbitmq-stomp#115

Core Server

Enhancements

• New configuration file format

  RabbitMQ now supports a new configuration file format.
  The format is based on sysctl
  and is similar to .ini files. Erlang term configuration files are still supported, it is also
  possible to combine the two formats (use both rabbitmq.conf and advanced.config).

  Most documentation examples were updated to use both new and classic config formats. See the docs
  at next.rabbitmq.com, in particular the configuration guide,
  for more information.

  GitHub issues: rabbitmq-server#550,
  rabbitmq-server#1103,
  rabbitmq-auth-backend-ldap#59

• Pluggable cluster peer discovery

  Automatic clustering for blank (without an existing database) nodes now can discover
  peers using pluggable backends. This is a set of features adopted from the rabbitmq-autocluster plugin by Gavin Roy.
  Two implementations are available out of the box: one uses a config file- and another DNS A records.
  Several more are available via plugins:

  • AWS
  • Consul
  • etcd
  • Kubernetes

  GitHub issues: rabbitmq-server#486, rabbitmq-server#988, rabbitmq-server#1143
  rabbitmq-server#1202, rabbitmq-server#1171, rabbitmq-server#1257, rabbitmq-server#1247

• Nodes in a cluster now can be restared in arbitrary order. They will attempt to contact
  one of the previously seen peers periodically (10 times with 30 second intervals by default).

  GitHub issue: rabbitmq-server#1022,
  rabbitmq-server#487

• Every virtual host now has separate message stores.
  This improves resiliency and reduces contention in multitenant environments,
  plus makes development of tools that perform backups and recovery of resting data easier
  in the future.

  During the upgrade nodes will migrate data to this new layout. This can take some time.
  To reduce the amount of time, drain as many queues as possible before upgrading, e.g.
  by stopping publishers without stopping consumers for a period of time.

  GitHub issues: rabbitmq-server#567, rabbitmq-server#1146, rabbitmq-server#1280,
  rabbitmq-management#446, rabbitmq-server#1303, rabbitmq-management#460, rabbitmq-server#1321

• New LevelDB-based message store index plugin.

  GitHub issue: rabbitmq-server#838

• Support config file path values with and without file extensions

  RabbitMQ no longer requires RABBITMQ_CONFIG_FILE values to not have a .config or .conf suffix. It will try appending both suffixes as needed when searching for suitable config file(s) to load.

  Github Issue: rabbitmq-server#691

• Operators now can configure how many concurrent connections are allowed in a vhost.

  GitHub issue: rabbitmq-server#500

• Operators now can configure how many queues can exist in a vhost.

  GitHub issue: rabbitmq-server#501

• Operator policies: their definitions are merged with the standard (user) policies and allow operators put global
  limits in place, e.g. max queue length or message TTL.

  GitHub issue: rabbitmq-server#930

• It is now possible to configure a limited prefetch value for all newly opened channels by default.
  This helps prevent consumers that never acknowledge deliveries from exhausting server resources.
  It is important to make sure that consumers that use manual acknowledgements can cope with this
  change before enabling it.

  GitHub issue: rabbitmq-server#1367

• Plugin version constraints

  RabbitMQ now has a mechanism for plugin authors to indicate what versions a plugin is compatible with.
  Incompatible plugins are logged and ignored.

  Github issues: rabbitmq-server#591, rabbitmq-server#735, rabbitmq-server#1090

• Lager-based logging: less [not prone to overload](https://s3.us-...

RabbitMQ 3.6.14

RabbitMQ 3.6.14

RabbitMQ 3.6.14 is a maintenance release that primarily fixes an issue in systemd
unit files that affected some systems. It is virtually identical to 3.6.13
otherwise.

Upgrades and Compatibility

See the "Upgrading clusters" section of the documentation
for general documentation on upgrades.

This release has no known incompatibilities with versions 3.6.7 through 3.6.13.
See the upgrade and compatibility sections in the 3.6.7 release notes if upgrading from an earlier release.

3.6.x Series Support Timeline

Please read this node on RabbitMQ 3.6.x series support timeline.

Debian and RPM packages

Bug Fixes

• systemd service unit no longer has trailing comments that could lead nodes
  into restart loops on some systems.

  GitHub issues: rabbitmq-server#1422

Management Plugin

Bug Fix

• Expandable sections on node metrics page failed to expand.

  GitHub issues: rabbitmq-management#507

Upgrading

To upgrade a non-clustered RabbitMQ simply install the new version. All configuration and persistent message data are retained.
When upgrading using definitions export/import from versions earlier than 3.6.0, see http://rabbitmq.com/passwords.html.

To upgrade a RabbitMQ cluster, follow the instructions in RabbitMQ documentation.

Source code archives

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.6.13.tar.gz.

RabbitMQ 3.6.13

RabbitMQ 3.6.13

RabbitMQ 3.6.13 is a maintenance release.

Upgrades and Compatibility

See the "Upgrading clusters" section of the documentation
for general documentation on upgrades.

This release has no known incompatibilities with versions 3.6.7 through 3.6.12.
See the upgrade and compatibility sections in the 3.6.7 release notes if upgrading from an earlier release.

3.6.x Series Support Timeline

Please read this node on RabbitMQ 3.6.x series support timeline.

Core Server

Bug Fixes

• Memory usage monitor uses subprocesses a lot more sparingly. They are started
  roughly once a second or not started at all, depending on the strategy (e.g. on Windows
  Erlang VM allocator information is used instead).

  GitHub issues: rabbitmq-server#1343, rabbitmq-common#224

• Very busy queues are now more efficient at prioritizing consumers, avoiding
  consumer delivery blocking when relatively long running operations (e.g. bulk flushing
  of transient messages to disk) happen.

  GitHub issues: rabbitmq-server#1388, rabbitmq-server#1407

• Queue master strategies now take additional queue HA arguments into account.

  GitHub issue: rabbitmq-server#1371

• Logging to standard output using RABBITMQ_LOGS=- wasn't possible on Windows.

  GitHub issue: rabbitmq-server#1348

• Queue master locator name now can be specified as Erlang strings.

  GitHub issue: rabbitmq-server#1411

• Direct Erlang client connections could fail with obscure messages when
  target node was still booting.

  GitHub issue: rabbitmq-server#1356

Enhancements

• supervisor2 now can be used in environments that perform hot code upgrades.

  GitHub issue: rabbitmq-common#230

• systemd service file now white lists exit code 69.

  GitHub issue: rabbitmq-server-release#51

• Example systemd service file now includes service restart settings.

  GitHub issue: rabbitmq-server#1359

• Queue master locator strategy now can be configured using strings.

  GitHub issue: rabbitmq-server#1411

• Plugin activation avoids logs things that can be confusing.

  GitHub issue: rabbitmq-server#1364

Management Plugin

Enhancements

• Minor efficiency improvements around stats collection.

  GitHub issues: rabbitmq-common#235

• jQuery upgraded to 1.12.4.

  GitHub issue: rabbitmq-management#502

• UI improvements.

• More detailed memory use breakdown on the node page.

  GitHub issue: rabbitmq-management#500

• It is now possible to configure an HTTP API path prefix for the plugin.

  GitHub issue: rabbitmq-management#481

• Queue details page no longer truncates node name.

  GitHub issue: rabbitmq-management#473

• Policy name in queue and exchange info is now a link.

  GitHub issue: rabbitmq-management#493

• DELETE /api/connections/{name} is now more defensive.

  GitHub issue: rabbitmq-management#497

Upgrading

To upgrade a non-clustered RabbitMQ simply install the new version. All configuration and persistent message data are retained.
When upgrading using definitions export/import from versions earlier than 3.6.0, see http://rabbitmq.com/passwords.html.

To upgrade a RabbitMQ cluster, follow the instructions in RabbitMQ documentation.

Source code archives

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.6.13.tar.gz.