Skip to content

RabbitMQ 4.1.6

Choose a tag to compare

@michaelklishin michaelklishin released this 17 Nov 02:23
· 20 commits to v4.1.x since this release
4a9806c

RabbitMQ 4.1.6 is a maintenance release in the 4.1.x release series.

It is strongly recommended that you read 4.1.0 release notes
in detail if upgrading from a version prior to 4.1.0.

Minimum Supported Erlang Version

RabbitMQ and Erlang/OTP Compatibility Matrix has more details on Erlang version requirements for RabbitMQ.

Nodes will fail to start on older Erlang releases.

Changes Worth Mentioning

Release notes can be found on GitHub at rabbitmq-server/release-notes.

Core Server

Bug Fixes

  • Enabling the khepri_db feature flag while the Log Exchange
    was enabled could cause a RabbitMQ node to run out of memory and crash.

    GitHub issues: #14069, #14796

  • Feature flag state in the registry and on disk were not consistent for a period of time during node boot.

    GitHub issue: #14943

CLI Tools

Bug Fixes

  • rabbitmqctl export_definitions could incorrectly serialize policy and operator policy
    definitions.

    GitHub issue: #14800

MQTT Plugin

Bug Fixes

  • Resource alarm handling now uses more context: it is aware of individual resources.
    When a cluster had multiple resource alarms (namely for memory footprint and free disk space)
    in effect, the blocking state was prematurely cleared when only one resource alarm was.

    GitHub issue: #14795

STOMP Plugin

Bug Fixes

  • Resource alarm handling now uses more context: it is aware of individual resources.
    When a cluster had multiple resource alarms (namely for memory footprint and free disk space)
    in effect, the blocking state was prematurely cleared when only one resource was [cleared].

    GitHub issue: #14795

Web MQTT Plugin

Bug Fixes

  • Resource alarm handling now uses more context: it is aware of individual resources.
    When a cluster had multiple resource alarms (namely for memory footprint and free disk space)
    in effect, the blocking state was prematurely cleared when only one resource was [cleared].

    GitHub issue: #14795