RabbitMQ 4.4.1 is a maintenance release in the 4.4.x release series.
It is strongly recommended that you read 4.4.0 release notes
in detail if upgrading from a version prior to 4.4.0.
Minimum Supported Erlang Version
The minimum supported Erlang version for this release series is 27.0.
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
-
Definition import on boot could hang on Erlang 28 because of a missing dependency
between boot steps. -
Virtual host records written by older versions could have their limits set to
undefined,
which made definition export fail.GitHub issue: #18137
-
Definition export no longer includes bindings to exclusive queues, and definition import
skips bindings toamq.*queues with a warning instead of failing.Contributed by @gomoripeti.
GitHub issue: #17838
-
Definition export no longer includes bindings of queues that were concurrently deleted,
and definition import skips bindings of missing server-named queues.GitHub issue: #17841
-
A quorum queue leader health check could report a queue with a leader as unhealthy, for example
after a leadership change or when the node running the check did not host a replica.Contributed by @Ayanda-D.
GitHub issue: #18274
-
When a new quorum queue member is started, the lowest
ramachine version among the
reachable members is now used. -
The quorum queue message expiration timer is now capped at one year.
GitHub issue: #17815
-
The metadata store now waits for Raft members with a capped timeout, which avoids an endless
retry loop in some operational scenarios. -
Classic queue CRC32 checksums are now calculated in a way that is compatible with future Erlang releases.
-
Classic queues: a crash report for a deleted queue now shows the original error.
GitHub issue: #18208
-
Message conversion between AMQP 0-9-1 and AMQP 1.0 no longer fails on
decimal
andnullheader values, nor onfloat,doubleandnullannotation values
set by the AMQP 1.0modifiedoutcome. -
Hourly log file rotation (for example,
log.file.rotation.date = $H30) never rotated the file.Contributed by @bellCold.
-
Streams now handle non-string
x-stream-filter-valuevalues gracefully.GitHub issue: #18147
-
AMQP 0-9-1 header and argument tables are validated more strictly.
-
AMQP 1.0 frames are validated more strictly.
-
AMQP 1.0 SQL filter expressions are evaluated more defensively.
GitHub issue: #18302
-
An AMQP 1.0 session no longer crashes when its writer process has already exited
during connection closure.GitHub issue: #18070
-
Credential expiry handling improvements.
-
Proxy Protocol handling improvements.
GitHub issue: #17995
-
Dead lettering validates its targets more strictly.
GitHub issue: #18195
-
Channels now send
channel.close-okwith a short socket write timeout.GitHub issue: #18242
Enhancements
-
AMQP 0-9-1 channels now use flow control when sending to the connection's socket writer process.
GitHub issue: #18049
-
Closing a non-AMQP 0-9-1 connection (for example, an MQTT, STOMP, stream or AMQP 1.0 connection)
is now cheaper on nodes with many tracked channels.GitHub issue: #18139
-
Policy names and definitions, as well as global runtime parameter names and values, are now
subject to size limits. The defaults are well above realistically used values.# the defaults are 1 KiB for the name and 64 KiB for the definition policies.max_name_length = 1024 policies.max_definition_size = 65536 # the defaults are 1 KiB for the name and 128 KiB for the value runtime_parameters.global.max_name_length = 1024 runtime_parameters.global.max_value_size = 131072
-
Stream segment files now enforce a minimum size of 4,096 bytes. Note that virtually all installations
use and should use values in megabytes, not kilobytes.GitHub issue: #18023
CLI Tools
Bug Fixes
-
rabbitmqctl reset,rabbitmqctl join_clusterand similar commands are now aware of the node boot state. -
CLI tools and peer discovery now refuse to remove cluster members that are still booting.
GitHub issue: #18232
-
rabbitmqctl export_definitionsfile permission handling improvements.GitHub issue: #18083
Stream Plugin
Bug Fixes
-
Stream protocol authentication is validated more strictly.
GitHub issue: #17936
Management Plugin
Bug Fixes
-
HTTP API endpoints that accept JSON request bodies now require the
content-typeheader to beapplication/json.GitHub issue: #18196
-
Several HTTP API endpoints that previously required previleged tagging of the use now require the
administratortag. -
Publishing via the HTTP API is now refused when a resource alarm is in effect.
GitHub issue: #18057
-
Queue, stream and exchange names that are not valid UTF-8 are now rejected with a
400 Bad Request. -
CORS handling improvements.
GitHub issue: #18032
-
An example
rabbitmq.conffile could not be generated from the management plugin's schema.Contributed by @wn1331.
Enhancements
-
The polling consumer (
POST /api/queues/{vhost}/{name}/get) endpoint now limits how many messages
and payload bytes a single request can return:# the defaults are 1000 messages and 64 MiB management.polling_consumer.max_messages = 1000 management.polling_consumer.max_payload_bytes = 67108864
GitHub issue: #17953
-
HTTP API JSON request body decoding now uses less memory with larger payloads.
GitHub issue: #18152
Prometheus Plugin
Bug Fixes
-
Exchange metric labels are now properly escaped.
GitHub issue: #17855
-
Several metrics that were reported as
untypedare now reported asgauge.GitHub issue: #17829
OAuth 2 AuthN and AuthZ Backend Plugin
Bug Fixes
-
Scope variable substitution is now more careful with claim values.
GitHub issue: #17935
-
More robust JWT decoding error handling.
Contributed by @markus812498.
GitHub issue: #17966
Shovel Plugin
Bug Fixes
-
Non-administrator users now must provide a password (or a token) in direct URIs,
including the URIs that use their own username.Administrators can still use direct URIs without a password.
GitHub issue: #18004
-
A shovel now drops messages that the destination refuses because they exceed its maximum message size,
instead of restarting over and over.GitHub issue: #18279
-
Deleting a shovel whose peer does not respond now takes at most about 10 seconds per side.
GitHub issue: #18086
-
AMQP 1.0 shovels no longer leave connections behind when connection setup times out.
GitHub issue: #18095
Enhancements
-
reconnect-delayis now validated more strictly.GitHub issue: #18110
-
Connection timeout is now limited to 180 seconds.
GitHub issue: #18037
Federation Plugins
Bug Fixes
-
In the
no-ackacknowledgement mode, an exchange federation link acknowledged the messages
it dropped, which led to link restarts in some scenarios.GitHub issue: #18112
-
Updating a
federation-upstream-setparameter restarted federation links in all virtual hosts.
Enhancements
-
reconnect-delayis now validated more strictly.GitHub issue: #18110
-
Connection timeout is now limited to 180 seconds.
GitHub issue: #18037
MQTT Plugin
Bug Fixes
-
Retained messages were lost when the metadata store was migrated to Khepri.
-
A retained Will message with a Will Delay Interval could not be delivered to subscribers.
Contributed by @himanxhugaur.
GitHub issue: #18225
Enhancements
-
The number of topic filters and user properties per packet is now limited:
# the defaults are 512 mqtt.max_topic_filters_per_packet = 512 mqtt.max_user_properties_per_packet = 512
GitHub issue: #18025
-
Message expiration is now limited to 10 years, consistent with other protocols.
Contributed by @himanxhugaur.
GitHub issue: #18141
STOMP Plugin
Bug Fixes
-
Consumer deliveries were not included in global message rates (a regression in
4.4.0). -
STOMP connections were not fully integrated with connection tracking (a regression in
4.4.0).GitHub issue: #17926
-
The connection process heap size limit used during authentication was not lifted after
login (a regression in4.4.0).GitHub issue: #18122
-
Queue access checks for
SUBSCRIBEframes are now consistent with other protocols.GitHub issue: #17933
-
CONNECTframes that have nologinorpasscodeheader are now refused early.GitHub issue: #17934
-
Message priority handling improvements.
-
Transaction handling improvements.
GitHub issue: #18038
Enhancements
-
Message expiration is now limited to 10 years, consistent with other protocols.
Contributed by @himanxhugaur.
GitHub issue: #18141
LDAP AuthN and AuthZ Backend Plugin
Bug Fixes
-
A pooled LDAP connection is now purged after a timeout or a late reply.
GitHub issue: #17984
-
Query pre-processing and password validation improvements.
Enhancements
-
auth_ldap.dn_lookup_bind.passwordandauth_ldap.other_bind.passwordnow support
encrypted values.GitHub issue: #17879
Event Exchange Plugin
Enhancements
-
Runtime parameter values are no longer included in the events by default.
A new setting controls this behavior:event_exchange.runtime_parameters.include_value = falseGitHub issue: #18148
Sharding Plugin
Enhancements
-
The number of shards per node is now limited to 4096.
GitHub issue: #17927
Web STOMP Examples Plugin
Enhancements
-
The examples now use
@stomp/stompjs7.5.0.GitHub issue: #18265
Erlang AMQP 0-9-1 Client
Bug Fixes
-
Direct channel
flushcalls now get a reply.Contributed by @yagogarea.
GitHub issue: #18306
-
The negotiated
frame_maxvalue is validated more strictly.GitHub issue: #18108
-
TLS certificate and key file paths must now point to regular files.
GitHub issue: #18109
Erlang AMQP 1.0 Client
Bug Fixes
-
Two processes were left running after a failed connection.
GitHub issue: #18093
-
The maximum frame size is now limited to a range between 512 bytes and 16 MiB.
GitHub issue: #18096