RABBITMQ-4.3.3 release notes and known issues

Summary

RabbitMQ 4.3.3 is a maintenance release in the 4.3.x release series . It is strongly recommended that you read 4.3.0 release notes in detail if upgrading from a version prior to 4.3.0 . Minimum Supported Erlang Version Important : starting with this release, the minimum supported Erlang version is 27.0 . Erlang/OTP 26 has reached end of life and is no longer supported. GitHub issue: #16914 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 Quorum queue, Khepri and other Raft leaders could optimistically commit new log entries in certain scenarios. GitHub issue: rabbitmq/ra#637 Quorum queues that use at-least-once dead lettering could get their dead lettering process permanently stuck after repeated queue membership changes. GitHub issue: #16652 Classic queue index directory paths could accumulate slashes, eventually failing with an enametoolong file system error. GitHub issue: #16833 Enabling the tie_binding_to_dest_with_keep_while_cond feature flag could fail with an exception when certain exchange-to-exchange topologies. GitHub issue: #16824 An invalid consumer_timeout value in the configuration now falls back to the default value (24 hours) instead of being used as is. GitHub issue: #16799 AMQP 1.0 management operations that declare an exchange with an alternate exchange now verify the necessary permissions on the alternate exchange, matching AMQP 0-9-1. GitHub issue: #16785 AMQP 1.0 management GET /bindings operations now behave consistently with the rest of the binding-related handlers. GitHub issue: #16790 Worker pool processes no longer terminate when they receive an unexpected message. Contributed by @Ayanda-D . GitHub issue: #16666 A race condition between concurrent queue (or virtual host) deletion and a Ra cluster shutdown could log an exception. Contributed by @Ayanda-D . GitHub issue: #16880 A closing channel (connection) that failed to send channel.close_ok on an already terminated writer or socket no longer produce log noise. Contributed by @Ayanda-D . GitHub issue: #16651 Unexpected failures during channel termination cleanup no longer produce log noise. Contributed by @Ayanda-D . GitHub issue: #16740 Code paths that use rabbit_queue_type_util:erpc_call/5 now handle more errors. Contributed by @Ayanda-D . GitHub issue: #16701 Nodes could fail to start with a bad_generator exception in rabbit_queue_decorator:select/1 when a quorum queue record in the metadata store had its decorators set to undefined . GitHub issues: #16843 , #16844 Enabling tracing on multiple virtual hosts concurrently could silently drop some of the virtual hosts from the traced set. All virtual host tracing state modifications are now linearized. GitHub issues: #16755 , #16763 Enhancements Password salts are now generated using a cryptographically secure pseudo-random number generator (CSPRNG). GitHub issue: #16775 Socket-level metric collection used by several protocol readers and the management agent now handles concurrently closed connections safely. Inspired by a contribution of @MugemaneBertin2001 . GitHub issues: #16856 , #16832 CLI Tools Bug Fixes rabbitmq-plugins commands now tolerate plugins that are listed as enabled but are not installed. GitHub issue: #16896 rabbitmq-plugins list no longer outputs an empty plugin table when the target node cannot be reached. GitHub issue: #16791 rabbitmq-plugins commands now correctly handle file paths of remote nodes, validate remote nodes in offline mode, and no longer report false positives for rabbitmq-plugins is_enabled . GitHub issue: #16842 Shell (Bash, zsh) command completion fixes. Contributed by @Chr1s70ph . GitHub issue: #16776 Enhancements rabbitmq-queues and rabbitmq-streams now provide transfer_leadership commands for individual queues and streams. GitHub issue

Improvements and security content

• RabbitMQ 4.3.3 is a maintenance release in the 4.3.x release series . It is strongly recommended that you read 4.3.0 release notes in detail if upgrading from a version prior to 4.3.0 . Minimum Supported Erlang Version Important : starting with this release, the minimum supported Erlang version is 27.0 . Erlang/OTP 26 has reached end of life and is no longer supported. GitHub issue: #16914 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 Quorum queue, Khepri and other Raft leaders could optimistically commit new log entries in certain scenarios. GitHub issue: rabbitmq/ra#637 Quorum queues that use at-least-once dead lettering could get their dead lettering process permanently stuck after repeated queue membership changes. GitHub issue: #16652 Classic queue index directory paths could accumulate slashes, eventually failing with an enametoolong file system error. GitHub issue: #16833 Enabling the tie_binding_to_dest_with_keep_while_cond feature flag could fail with an exception when certain exchange-to-exchange topologies. GitHub issue: #16824 An invalid consumer_timeout value in the configuration now falls back to the default value (24 hours) instead of being used as is. GitHub issue: #16799 AMQP 1.0 management operations that declare an exchange with an alternate exchange now verify the necessary permissions on the alternate exchange, matching AMQP 0-9-1. GitHub issue: #16785 AMQP 1.0 management GET /bindings operations now behave consistently with the rest of the binding-related handlers. GitHub issue: #16790 Worker pool processes no longer terminate when they receive an unexpected message. Contributed by @Ayanda-D . GitHub issue: #16666 A race condition between concurrent queue (or virtual host) deletion and a Ra cluster shutdown could log an exception. Contributed by @Ayanda-D . GitHub issue: #16880 A closing channel (connection) that failed to send channel.close_ok on an already terminated writer or socket no longer produce log noise. Contributed by @Ayanda-D . GitHub issue: #16651 Unexpected failures during channel termination cleanup no longer produce log noise. Contributed by @Ayanda-D . GitHub issue: #16740 Code paths that use rabbit_queue_type_util:erpc_call/5 now handle more errors. Contributed by @Ayanda-D . GitHub issue: #16701 Nodes could fail to start with a bad_generator exception in rabbit_queue_decorator:select/1 when a quorum queue record in the metadata store had its decorators set to undefined . GitHub issues: #16843 , #16844 Enabling tracing on multiple virtual hosts concurrently could silently drop some of the virtual hosts from the traced set. All virtual host tracing state modifications are now linearized. GitHub issues: #16755 , #16763 Enhancements Password salts are now generated using a cryptographically secure pseudo-random number generator (CSPRNG). GitHub issue: #16775 Socket-level metric collection used by several protocol readers and the management agent now handles concurrently closed connections safely. Inspired by a contribution of @MugemaneBertin2001 . GitHub issues: #16856 , #16832 CLI Tools Bug Fixes rabbitmq-plugins commands now tolerate plugins that are listed as enabled but are not installed. GitHub issue: #16896 rabbitmq-plugins list no longer outputs an empty plugin table when the target node cannot be reached. GitHub issue: #16791 rabbitmq-plugins commands now correctly handle file paths of remote nodes, validate remote nodes in offline mode, and no longer report false positives for rabbitmq-plugins is_enabled . GitHub issue: #16842 Shell (Bash, zsh) command completion fixes. Contributed by @Chr1s70ph . GitHub issue: #16776 Enhancements rabbitmq-queues and rabbitmq-streams now provide transfer_leadership commands for individual queues and streams. GitHub issue

Affected products and versions

Recommended action

Review the official publisher document before deployment.

Official publisher evidence