Skip to content

Releases: rabbitmq/rabbitmq-server

RabbitMQ 3.7.14-rc.1

22 Mar 10:52
@pivotal-rabbitmq-ci pivotal-rabbitmq-ci
v3.7.14-rc.1
2f5ef79

Choose a tag to compare

View all tags
RabbitMQ 3.7.14-rc.1 Pre-release
Pre-release

RabbitMQ 3.7.14-rc.1

RabbitMQ 3.7.14-rc.1 is a preview maintenance release. It focuses on bug fixes and
minor usability improvements. This release requires Erlang/OTP 20.3 or later.

Erlang/OTP Compatibility Notes

Per the new Erlang version support policy in effect starting with January 2019,
this release no longer supports Erlang/OTP 19.3.
Make sure a supported Erlang version is used before upgrading.

Provisioning Latest Erlang Releases
explains what package repositories and tools can be used to provision latest patch versions of
Erlang 20.3.x and 21.x.

Compatibility Notes

Minimum Required Erlang Version

This release requires Erlang/OTP 20.3 or later.

Upgrading to Erlang 21.x

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.

Upgrade Doc Guides and Change Log

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 and
RabbitMQ change log for release notes of other releases.

Getting Help

Any questions about this release, upgrades or RabbitMQ in general are welcome on the
RabbitMQ mailing list.

Changes

Core Server

Bug Fixes

Enhancements

  • TCP and TLS listeners are started later to reduce the probability of clients connecting to and performing operations
    on a node that's not fully initialised.

    GitHub issue: rabbitmq/rabbitmq-server#1869

  • Reduced schema data store locking for binding operations.

    GitHub issue: rabbitmq/rabbitmq-server#1900

CLI Tools

Enhancements

  • More informative and user-friendly help messages produced by help and help [command] commands.

    GitHub issue: rabbitmq/rabbitmq-cli#332

Management Plugin

Bug Fixes

Enhancements

Federation Plugin

Bug Fixes

RPM Package

Bug Fixes

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

Loading

RabbitMQ 3.7.13

07 Mar 22:01
@pivotal-rabbitmq-ci pivotal-rabbitmq-ci
v3.7.13
a124288
This commit was signed with the committer’s verified signature.
lukebakken Luke Bakken
GPG key ID: B707DD932540186E
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
RabbitMQ 3.7.13

RabbitMQ 3.7.13

RabbitMQ 3.7.13 is a maintenance release. It focuses on bug fixes and
minor usability improvements. This release requires Erlang/OTP 20.3 or later.

Erlang/OTP Compatibility Notes

Per the new Erlang version support policy in effect starting with January 2019,
this release no longer supports Erlang/OTP 19.3.
Make sure a supported Erlang version is used before upgrading.

Provisioning Latest Erlang Releases
explains what package repositories and tools can be used to provision latest patch versions of
Erlang 20.3.x and 21.x.

Compatibility Notes

Minimum Required Erlang Version

This release requires Erlang/OTP 20.3 or later.

Upgrading to Erlang 21.x

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.

Upgrade Doc Guides and Change Log

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 and
RabbitMQ change log for release notes of other releases.

Getting Help

Any questions about this release, upgrades or RabbitMQ in general are welcome on the
RabbitMQ mailing list.

Changes

Core Server

Bug Fixes

Enhancements

CLI Tools

Enhancements

  • 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: rabbitmq/rabbitmq-cli#327.

  • rabbitmqctl forget_cluster_node produces a more helpful error message when asked to remove a node with running
    RabbitMQ application.

    GitHub issue: rabbitmq/rabbitmq-cli#323

  • New command, rabbitmqctl force_gc, that requests fullsweep GC for all processes on the target node.

    GitHub issue: rabbitmq/rabbitmq-cli#319

  • All RabbitMQ CLI tools now support --version as well as version as a command.

    GitHub issue: rabbitmq/rabbitmq-cli#314

Management Plugin

Bug Fixes

Debian and RPM Packages

Bug Fixes

Federation Plugin

Bug Fixes

Shovel Plugin

Bug Fixes

HTTP AuthN/AuthZ Backend Plugin

Enhnanceements

Trust Store Plugin

Bug Fixes

  • HTTP provider did not correctly update If-Modified-Since request header when certificates
    (and thus their Last-Modified response header) were updated.

    GitHub issue: rabbitmq/rabbitmq-trust-store#68

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

Loading

RabbitMQ 3.8.0-beta.3

08 Mar 00:52
@pivotal-rabbitmq-ci pivotal-rabbitmq-ci
v3.8.0-beta.3
b5b8ecd

Choose a tag to compare

View all tags
RabbitMQ 3.8.0-beta.3 Pre-release
Pre-release 
v3.8.0-beta.3

Release 3.8.0-beta.3
Loading

RabbitMQ 3.7.13-rc.2

28 Feb 20:30
@pivotal-rabbitmq-ci pivotal-rabbitmq-ci
v3.7.13-rc.2
a124288
This commit was signed with the committer’s verified signature.
lukebakken Luke Bakken
GPG key ID: B707DD932540186E
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
RabbitMQ 3.7.13-rc.2 Pre-release
Pre-release

RabbitMQ 3.7.13-rc.2

RabbitMQ 3.7.13-rc.2 is a maintenance release candidate. It focuses on bug fixes and
minor usability improvements. This release requires Erlang/OTP 20.3 or later.

Erlang/OTP Compatibility Notes

Per the new Erlang version support policy in effect starting with January 2019,
this release no longer supports Erlang/OTP 19.3.
Make sure a supported Erlang version is used before upgrading.

Provisioning Latest Erlang Releases
explains what package repositories and tools can be used to provision latest patch versions of
Erlang 20.3.x and 21.x.

Compatibility Notes

Minimum Required Erlang Version

This release requires Erlang/OTP 20.3 or later.

Upgrading to Erlang 21.x

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.

Upgrade Doc Guides and Change Log

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 and
RabbitMQ change log for release notes of other releases.

Getting Help

Any questions about this release, upgrades or RabbitMQ in general are welcome on the
RabbitMQ mailing list.

Changes

Core Server

Bug Fixes

Enhancements

CLI Tools

Enhancements

  • rabbitmqctl forget_cluster_node produces a more helpful error message when asked to remove a node with running
    RabbitMQ application.

    GitHub issue: rabbitmq/rabbitmq-cli#323

  • New command, rabbitmqctl force_gc, that requests fullsweep GC for all processes on the target node.

    GitHub issue: rabbitmq/rabbitmq-cli#319

  • All RabbitMQ CLI tools now support --version as well as version as a command.

    GitHub issue: rabbitmq/rabbitmq-cli#314

Debian and RPM Packages

Bug Fixes

Shovel Plugin

Bug Fixes

HTTP AuthN/AuthZ Backend Plugin

Enhnanceements

Trust Store Plugin

Bug Fixes

  • HTTP provider did not correctly update If-Modified-Since request header when certificates
    (and thus their Last-Modified response header) were updated.

    GitHub issue: rabbitmq/rabbitmq-trust-store#68

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

Loading

RabbitMQ 3.7.13-beta.1

22 Feb 18:20
@pivotal-rabbitmq-ci pivotal-rabbitmq-ci
v3.7.13-beta.1
815b182
This commit was signed with the committer’s verified signature.
dumbbell Jean-Sébastien Pédron
GPG key ID: 39E99761A5FD94CC
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
RabbitMQ 3.7.13-beta.1 Pre-release
Pre-release

RabbitMQ 3.7.13-beta.1

RabbitMQ 3.7.13-beta.1 is a preview of a maintenance release. It focuses on bug fixes and
minor usability improvements. This release requires Erlang/OTP 20.3 or later.

Erlang/OTP Compatibility Notes

Per the new Erlang version support policy in effect starting with January 2019,
this release no longer supports Erlang/OTP 19.3.
Make sure a supported Erlang version is used before upgrading.

Provisioning Latest Erlang Releases
explains what package repositories and tools can be used to provision latest patch versions of
Erlang 20.3.x and 21.x.

Compatibility Notes

Minimum Required Erlang Version

This release requires Erlang/OTP 20.3 or later.

Upgrading to Erlang 21.x

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.

Upgrade Doc Guides and Change Log

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 and
RabbitMQ change log for release notes of other releases.

Getting Help

Any questions about this release, upgrades or RabbitMQ in general are welcome on the
RabbitMQ mailing list.

Changes

Core Server

Bug Fixes

Enhancements

  • Exclusive queue property mismatch during queue declaration now produces a more helpful
    error message.

    GitHub issue: rabbitmq/rabbitmq-server#1887

CLI Tools

Enhancements

  • New command, rabbitmqctl force_gc, that requests fullsweep GC for all processes on the target node.

    GitHub issue: rabbitmq/rabbitmq-cli#319

  • All RabbitMQ CLI tools now support --version as well as version as a command.

    GitHub issue: rabbitmq/rabbitmq-cli#314

Debian and RPM Packages

Bug Fixes

Shovel Plugin

Bug Fixes

Trust Store Plugin

Bug Fixes

  • HTTP provider did not correctly update If-Modified-Since request header when certificates
    (and thus their Last-Modified response header) were updated.

    GitHub issue: rabbitmq/rabbitmq-trust-store#68

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

Loading

RabbitMQ 3.7.12

15 Feb 09:35
@pivotal-rabbitmq-ci pivotal-rabbitmq-ci
v3.7.12
e7a4778

Choose a tag to compare

View all tags
RabbitMQ 3.7.12

RabbitMQ 3.7.12

RabbitMQ 3.7.12 is a maintenance release. It focuses on bug fixes and
minor usability improvements. This release requires Erlang/OTP 20.3 or later.

Erlang/OTP Compatibility Notes

Per the new Erlang version support policy in effect starting with January 2019,
this release no longer supports Erlang/OTP 19.3.
Make sure a supported Erlang version is used before upgrading.

Provisioning Latest Erlang Releases
explains what package repositories and tools can be used to provision latest patch versions of
Erlang 20.3.x and 21.x.

Compatibility Notes

Minimum Required Erlang Version

This release requires Erlang/OTP 20.3 or later.

rabbitmqctl shutdown Behavior with Remote Nodes

In earlier releases, when rabbitmqctl shutdown was used against a remote node, it would successfully
shut down the node but won't actually wait for its termination because the pid file path
reported by the remote node is not available locally. This is because rabbitmqctl shutdown was
meant to be used as a rabbitmqctl stop alternative that doesn't require the caller to know the
pid file path.

Starting with this version, rabbitmqctl shutdown will refuse to run against a remote node
by default. If the earlier behavior is desired and expected, it can be restored by passing --no-wait:

# will refuse to run against a remote node in --wait mode as of 3.7.12
# and --wait is on by default
rabbitmqctl shutdown -n [email protected] --longnames

# behaves the same way as in 3.7.0 through 3.7.11
rabbitmqctl shutdown -n [email protected] --longnames --no-wait

inet_dist_listen_min and inet_dist_listen_max in New Style Configuration

inet_dist_listen_min and inet_dist_listen_max were removed from new style configuration.
They wouldn't have any effect due to how configuration translation is performed.
Use advanced.config or the RABBITMQ_DIST_PORT env variable to configure these settings:

[
 {kernel, [
   {inet_dist_listen_min, 33672},
   {inet_dist_listen_max, 33672}
 ]},
 {rabbit, [
   %% ...
 ]}
].

Note that some runtime parameters, e.g. net_ticktime, can be set via new style configuration.
This change is specific to the distirbution port settings.

Upgrading to Erlang 21.x

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.

Upgrade Doc Guides and Change Log

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 and
RabbitMQ change log for release notes of other releases.

Getting Help

Any questions about this release, upgrades or RabbitMQ in general are welcome on the
RabbitMQ mailing list.

Changes

Core Server

Bug Fixes

  • When a node was configured to allow for unlimited frame size, an empty message published
    via HTTP API resulted in an infinite recursion loop in the parser.

    GitHub issue: rabbitmq/rabbitmq-common#299

  • inet_dist_listen_min and inet_dist_listen_max were removed from new style configuration.
    They wouldn't have any effect due to how configuration translation is performed.
    Use advanced.config or the RABBITMQ_DIST_PORT env variable to configure these settings:

    [
  {kernel, [
    {inet_dist_listen_min, 33672},
    {inet_dist_listen_max, 33672}
  ]},
  {rabbit, [
    %% ...
  ]}
].

    Note that some runtime parameters, e.g. net_ticktime, can be set via new style configuration.
    This change is specific to the distirbution port settings.

    Contributed by Gabriele Santomaggio.

    GitHub issue: rabbitmq/rabbitmq-server#1881

CLI Tools

Bug Fixes

  • rabbitmqctl and other CLI tools could fail when used with nodes using long node names.

    GitHub issue: rabbitmq/rabbitmq-cli#311

  • rabbitmqctl --help now exits with exit code of 0. rabbitmqctl (no arguments) uses code
    64 (EX_USAGE).

    GitHub issue: rabbitmq/rabbitmq-cli#307

Enhancements

  • rabbitmqctl shutdown now requires the user to opt in and provide --no-wait
    to be used with remote nodes. There are no behavior changes when the command is invoked
    against a locally running node. See also the compatibility note to this release.

    GitHub issue: rabbitmq/rabbitmq-cli#309

Management Plugin

Bug Fixes

MQTT Plugin

Enhancements

  • When a retained message is published, its topic is now correctly translated
    to use MQTT topic separators (a slash) regardless of the internal representation.

    Contributed by Ryan Sandbach.

    GitHub issue: rabbitmq/rabbitmq-mqtt#175

  • When a client sent a duplicate CONNECT frame (tried to "reauthenticate"), connection failed
    with a scary looking exception.

    Now the frame is ignored (reauthentication is therefore still impossible) and a warning is logged
    but the connection is kept open.

    Kudos to Grigory Starinkin for confirming our original hypothesis and providing the steps
    to reproduce.

    GitHub issue: rabbitmq/rabbitmq-mqtt#179.

Bug Fixes

LDAP Plugin

Enhancements

Shovel Plugin

Bug Fixes

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

Loading

RabbitMQ 3.7.12-rc.2

11 Feb 08:36
@pivotal-rabbitmq-ci pivotal-rabbitmq-ci
v3.7.12-rc.2
937e4ce

Choose a tag to compare

View all tags
RabbitMQ 3.7.12-rc.2 Pre-release
Pre-release

RabbitMQ 3.7.12 RC2

RabbitMQ 3.7.12-rc.2 is a preview of a maintenance release. It focuses on bug fixes and
minor usability improvements. This release requires Erlang/OTP 20.3
or later.

Erlang/OTP Compatibility Notes

Per the new Erlang version support policy in effect starting with January 2019,
this release no longer supports Erlang/OTP 19.3.
Make sure a supported Erlang version is used before upgrading.

Provisioning Latest Erlang Releases
explains what package repositories and tools can be used to provision latest patch versions of
Erlang 20.3.x and 21.x.

Compatibility Notes

Minimum Required Erlang Version

This release requires Erlang/OTP 20.3 or later.

rabbitmqctl shutdown Behavior with Remote Nodes

In earlier releases, when rabbitmqctl shutdown was used against a remote node, it would successfully
shut down the node but won't actually wait for its termination because the pid file path
reported by the remote node is not available locally. This is because rabbitmqctl shutdown was
meant to be used as a rabbitmqctl stop alternative that doesn't require the caller to know the
pid file path.

Starting with this version, rabbitmqctl shutdown will refuse to run against a remote node
by default. If the earlier behavior is desired and expected, it can be restored by passing --no-wait:

# will refuse to run against a remote node in --wait mode as of 3.7.12
# and --wait is on by default
rabbitmqctl shutdown -n [email protected] --longnames

# behaves the same way as in 3.7.0 through 3.7.11
rabbitmqctl shutdown -n [email protected] --longnames --no-wait

Upgrading to Erlang 21.x

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.

Upgrade Doc Guides and Change Log

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 and
RabbitMQ change log for release notes of other releases.

Getting Help

Any questions about this release, upgrades or RabbitMQ in general are welcome on the
RabbitMQ mailing list.

Changes

Core Server

Bug Fixes

  • When a node was configured to allow for unlimited frame size, an empty message published
    via HTTP API resulted in an infinite recursion loop in the parser.

    GitHub issue: rabbitmq/rabbitmq-common#299

CLI Tools

Bug Fixes

  • rabbitmqctl and other CLI tools could fail when used with nodes using long node names.

    GitHub issue: rabbitmq/rabbitmq-cli#311

  • rabbitmqctl --help now exits with exit code of 0. rabbitmqctl (no arguments) uses code
    64 (EX_USAGE).

    GitHub issue: rabbitmq/rabbitmq-cli#307

Enhancements

  • rabbitmqctl shutdown now requires the user to opt in and provide --no-wait
    to be used with remote nodes. There are no behavior changes when the command is invoked
    against a locally running node. See also the compatibility note to this release.

    GitHub issue: rabbitmq/rabbitmq-cli#309

MQTT Plugin

Enhancements

  • When a retained message is published, its topic is now correctly translated
    to use MQTT topic separators (a slash) regardless of the internal representation.

    Contributed by Ryan Sandbach.

    GitHub issue: rabbitmq/rabbitmq-mqtt#175

  • When a client sent a duplicate CONNECT frame (tried to "reauthenticate"), connection failed
    with a scary looking exception.

    Now the frame is ignored (reauthentication is therefore still impossible) and a warning is logged
    but the connection is kept open.

    Kudos to Grigory Starinkin for confirming our original hypothesis and providing the steps
    to reproduce.

    GitHub issue: rabbitmq/rabbitmq-mqtt#179.

Bug Fixes

LDAP Plugin

Enhancements

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

Loading

RabbitMQ 3.7.12-rc.1

08 Feb 00:36
@pivotal-rabbitmq-ci pivotal-rabbitmq-ci
v3.7.12-rc.1
7fe42d0

Choose a tag to compare

View all tags
RabbitMQ 3.7.12-rc.1 Pre-release
Pre-release

RabbitMQ 3.7.12 RC1

RabbitMQ 3.7.12-rc.1 is a preview of a maintenance release. It focuses on bug fixes and
minor usability improvements. This release requires Erlang/OTP 20.3
or later.

Erlang/OTP Compatibility Notes

Per the new Erlang version support policy in effect starting with January 2019,
this release no longer supports Erlang/OTP 19.3.
Make sure a supported Erlang version is used before upgrading.

Provisioning Latest Erlang Releases
explains what package repositories and tools can be used to provision latest patch versions of
Erlang 20.3.x and 21.x.

Compatibility Notes

Minimum Required Erlang Version

This release requires Erlang/OTP 20.3 or later.

rabbitmqctl shutdown Behavior with Remote Nodes

In earlier releases, when rabbitmqctl shutdown was used against a remote node, it would successfully
shut down the node but won't actually wait for its termination because the pid file path
reported by the remote node is not available locally. This is because rabbitmqctl shutdown was
meant to be used as a rabbitmqctl stop alternative that doesn't require the caller to know the
pid file path.

Starting with this version, rabbitmqctl shutdown will refuse to run against a remote node
by default. If the earlier behavior is desired and expected, it can be restored by passing --no-wait:

# will refuse to run against a remote node in --wait mode as of 3.7.12
# and --wait is on by default
rabbitmqctl shutdown -n [email protected] --longnames

# behaves the same way as in 3.7.0 through 3.7.11
rabbitmqctl shutdown -n [email protected] --longnames --no-wait

Upgrading to Erlang 21.x

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.

Upgrade Doc Guides and Change Log

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 and
RabbitMQ change log for release notes of other releases.

Getting Help

Any questions about this release, upgrades or RabbitMQ in general are welcome on the
RabbitMQ mailing list.

CLI Tools

Bug Fixes

  • rabbitmqctl and other CLI tools could fail when used with nodes using long node names.

    GitHub issue: rabbitmq/rabbitmq-cli#311

  • rabbitmqctl --help now exits with exit code of 0. rabbitmqctl (no arguments) uses code
    64 (EX_USAGE).

    GitHub issue: rabbitmq/rabbitmq-cli#307

Enhancements

  • rabbitmqctl shutdown now requires the user to opt in and provide --no-wait
    to be used with remote nodes. There are no behavior changes when the command is invoked
    against a locally running node. See also the compatibility note to this release.

    GitHub issue: rabbitmq/rabbitmq-cli#309

MQTT Plugin

Enhancements

  • When a retained message is published, its topic is now correctly translated
    to use MQTT topic separators (a slash) regardless of the internal representation.

    Contributed by Ryan Sandbach.

    GitHub issue: rabbitmq/rabbitmq-mqtt#175

Bug Fixes

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

Loading

RabbitMQ 3.8.0-beta.2

01 Feb 21:38
@pivotal-rabbitmq-ci pivotal-rabbitmq-ci
v3.8.0-beta.2
8b9036a
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
RabbitMQ 3.8.0-beta.2 Pre-release
Pre-release 
v3.8.0-beta.2

Release 3.8.0-beta.2
Loading

RabbitMQ 3.7.11

31 Jan 20:37
@pivotal-rabbitmq-ci pivotal-rabbitmq-ci
v3.7.11
e1b0cd5

Choose a tag to compare

View all tags
RabbitMQ 3.7.11

RabbitMQ 3.7.11

RabbitMQ 3.7.11 is a maintenance release. It focuses on bug fixes and
minor usability improvements. This is the first release to require Erlang/OTP 20.3+.

Erlang/OTP Compatibility Notes

Per the new Erlang version support policy in effect starting with January 2019,
this release drops support for Erlang/OTP 19.3. Make sure a supported Erlang version is used before upgrading.

Provisioning Latest Erlang Releases explains what package repositories and tools can be used to provision latest patch versions of Erlang 20.3.x and 21.x.

Compatibility Notes

  • This release requires Erlang/OTP 20.3 or later.
  • Default CLI command exit code has changed from 70 (EX_UNAVAILABLE) to 69 (EX_SOFTWARE).
    This does not affect all commands and all error conditions, e.g. argument validation still uses code 64 (EX_USAGE)

Upgrading to Erlang 21.x

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.

Documentation Guides and Change Log

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 and
RabbitMQ change log for release notes of other releases.

Changes

Core Server

Erlang Version Requirement

Bug Fixes

  • Number of socket file descriptors used is now correctly incremented.

    GitHub issue: rabbitmq/rabbitmq-management#652

  • Configuration schema file was not copied during upgrades.

    GitHub issues: rabbitmq/rabbitmq-server#1843

  • First heartbeat frame on a successfully negotiated connection is now sent after a half of the negotiated heartbeat
    timeout. Previously it was sent after a complete timeout. Since most connections have other activity after
    connection handshake is complete, this didn't have any visible effects on most systems.

    GitHub issue: rabbitmq/rabbitmq-common#293

  • If Syslog was configured to use TCP, the node could fail to start.

    GitHub issue: rabbitmq/rabbitmq-server#1850

CLI Tools

Enhancements

Management Plugin

Enhancements

  • rabbitmqadmin now defines an exception not available in Python 2, making TCP connection
    error reporting more similar with that on Python 3.

    GitHub issue: rabbitmq/rabbitmq-management#647

AWS Peer Discovery Plugin

Bug Fixes

STOMP Plugin

Enhancements

MQTT Plugin

Enhancements

AuthN/AuthZ Backend Cache Plugin

Bug Fixes

Erlang Client

Enhancements

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

Loading