Self-host RabbitMQ
v4.3.7Multi-protocol messaging and streaming broker
$ docker run -it --rm --name rabbitmq -p 5672:5672 -p 15672:15672 rabbitmq:4-management- Stars
- 13 960
- Ports
- 5672 (AMQP 0-9-1 and AMQP 1.0 client connections (non-TLS)), 5671 (AMQP 0-9-1 and AMQP 1.0 over TLS), 5552 (RabbitMQ Stream protocol clients (non-TLS)), 15672 (HTTP API, management UI and rabbitmqadmin (management plugin)), 15692 (Prometheus metrics export (Prometheus plugin)), 1883 (MQTT clients when the MQTT plugin is enabled), 61613 (STOMP clients when the STOMP plugin is enabled), 25672 (Inter-node and CLI tool communication (Erlang distribution port))
rabbitmqWhat is RabbitMQ?
RabbitMQ is a feature-rich open-source broker for messaging and streaming, widely used to decouple microservices, dispatch RPC-style work, buffer IoT connections and fan out event streams. One node accepts AMQP 0-9-1, AMQP 1.0, MQTT 3.x/5.0, STOMP 1.0-1.2 and the RabbitMQ Stream protocol, with MQTT and STOMP also available over WebSockets, so clients in many languages can talk to it over open standards without vendor lock-in. Messages travel through exchanges with routing and filtering, delivery can be acknowledged and confirmed, and durability comes from replicated quorum queues plus append-only, replicated streams with non-destructive consumers. Nodes form clusters, while federation and shovels chain deployments across datacenters or clouds. Day-to-day operation uses a browser-based management UI, an HTTP API, rabbitmqadmin and the rabbitmqctl CLI, and metrics can be scraped in Prometheus format with ready-made Grafana dashboards. Access control supports internal users plus LDAP, OAuth 2 and HTTP backends, and every protocol can run over TLS. You can run it yourself from the community Docker image, Team RabbitMQ's apt or RPM repositories, a generic UNIX binary, a Windows installer or Chocolatey package, Homebrew on macOS, or the Kubernetes cluster operator the vendor publishes for it. A supported Erlang/OTP release is required (packages install it for you). The broker itself is MPL-2.0 licensed and free; longer support lifecycles, disaster recovery and round-the-clock vendor support belong to the commercial Tanzu editions, and the default seeded user is restricted to localhost for safety.
RabbitMQ alternatives
VerneMQVerneMQ is a self-hosted, open-source MQTT broker built on Erlang/OTP that scales to handle millions of IoT connections with low latency and fault tolerance.CompareVerneMQ with RabbitMQ
automqSelf-hosted, open-source Apache Kafka fork with stateless brokers that store logs on S3 or MinIO and rebalance partitions in seconds.Compareautomq with RabbitMQ
MosquittoEclipse Mosquitto - An open source MQTT brokerCompareMosquitto with RabbitMQ
Eclipse MosquittoSelf-hosted open-source MQTT broker for MQTT 5.0, 3.1.1 and 3.1 with TLS, WebSockets, bridging, ACLs and a C client library plus CLI pub/sub tools.CompareEclipse Mosquitto with RabbitMQ
EMQXThe most scalable and reliable MQTT broker for AI, IoT, IIoT and connected vehiclesCompareEMQX with RabbitMQ
ejabberdejabberd is a self-hosted, open-source XMPP/MQTT/SIP server in Erlang, proven at massive scale with 2M+ concurrent users per node.Compareejabberd with RabbitMQ
nsqOpen-source self-hosted distributed messaging platform: push-based pub-sub over topics and channels, in-memory queues that spill to disk, plus the nsqadmin web UI.Comparensq with RabbitMQ
mqttuiMQTTUI is a self-hosted, open-source web app for monitoring and automating MQTT infrastructure with multi-broker support, rules engine, and alerting.Comparemqttui with RabbitMQ
Should you self-host RabbitMQ?
RabbitMQ scores 76/100 on selfhost.directory (how scoring works) and ranks #3 of 12 in Message Broker. It has 13 960 GitHub stars, +54 in the last 30 days.
It shipped 14 stable releases in the past year. The latest, v4.3.7, came out on 20 October 2026. New versions land roughly every 3 weeks.
Setup is moderate: expect some configuration beyond a single command. An official Docker image is available. It is Other-licensed and written mostly in JavaScript.
Its closest alternative on selfhost.directory is Apache Kafka (82/100, 34 203 stars). It scores higher overall, so compare the two before you pick. See RabbitMQ vs Apache Kafka side by side.
Features
- CLI administration tools
- Clustering and replication
- Federation
- Message acknowledgements and publisher confirms
- Message routing and filtering
- MQTT/STOMP over WebSockets
- Multi-protocol messaging
- Prometheus metrics endpoint
- Quorum queues
- REST/HTTP management API
- Shovel message forwarding
- Stream (log) consumption
- TLS Encryption
- Web-based management UI
RabbitMQ README
RabbitMQ is a feature rich, multi-protocol messaging and streaming broker. It supports:
- AMQP 1.0
- AMQP 0-9-1
- RabbitMQ Stream Protocol
- MQTT 3.1, 3.1.1, and 5.0
- STOMP 1.0 through 1.2
- MQTT over WebSocket
- STOMP over WebSocket
- AMQP 1.0 over WebSocket (supported in VMware Tanzu RabbitMQ)
How to install RabbitMQ
Install RabbitMQ with Docker
docker run -it --rm --name rabbitmq -p 5672:5672 -p 15672:15672 rabbitmq:4-management
Community-maintained official image on Docker Hub; the -management tag also enables the UI and HTTP API.
Install RabbitMQ with Debian
RABBITMQ_CONFIG_FILE, RABBITMQ_NODENAMEsudo apt-get update -ysudo apt-get install curl gnupg -y
Team RabbitMQ maintains two signed apt repositories; after adding the source list file under /etc/apt/sources.list.d/ the rabbitmq-server package is installed with apt (a supported Erlang/OTP series must be provisioned first, which the guide's quick-start script does).
Install RabbitMQ with Homebrew
brew update
Then, install RabbitMQ server with:
brew install rabbitmq
Core tap formula maintained by the Homebrew community; installing it does not start the node - use brew services start rabbitmq, and enable feature flags with rabbitmqctl.
How to configure RabbitMQ
RABBITMQ_DEFAULT_USERSeeds the default user; intended for development and CI environments.values: Username
RABBITMQ_DEFAULT_PASSSeeds the default user's password; intended for development and CI environments.values: Password
RABBITMQ_NODENAME=rabbit@$HOSTNAMENode name, unique per Erlang node and machine (rabbit@%COMPUTERNAME% on Windows).values: Erlang node name
RABBITMQ_CONFIG_FILEPath to the main rabbitmq.conf configuration file (location differs per packaging).values: File path
RABBITMQ_MNESIA_BASEBase directory for node database, message store and cluster state data.values: Directory path
RabbitMQ releases & version history
RabbitMQ 4.3.7 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
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
-
The
basic.cancelnotification sent on a consumer delivery timeout
now properly clears consumer state even if the client does not respond withbasic.cancel-ok.Most clients do not respond, and nodes older than
4.3.0do not accept a client-sent
basic.cancel-okat all. The server now advertises whether one is supported, and a short timeout
removes the consumer if the client never responds.A new
rabbitmq.confsetting controls what happens on such a timeout:# notify_consumer (the default) sends basic.cancel to clients that support # the consumer_cancel_notify capability and closes the channel for others # close_channel always closes the channel, which is the pre-4.3.0 behavior consumer_timeout_response = notify_consumer
GitHub issue: #17734
-
Classic queue expiration (
x-expires) timestamps were lost on node restart, so the queue
TTL timer did not fire when it was supposed to if the TTL outlived the restart. -
Routing to queues now handles concurrent queue deletion gracefully in more places, avoiding
confusing (and also non-actionable) exceptions.This also avoids unnecessary publisher confirm noise, most visible with transient exclusive
queues bound to a topic exchange. -
A quorum queue declaration that timed out waiting for a remote Khepri projection left
the queue metadata behind and prevented a retry with the same name.Contributed by @chenshi5012.
GitHub issue: #17550
-
Message conversion between AMQP 1.0 and AMQP 0-9-1 no longer fails on AMQP 1.0 values
that AMQP 0-9-1 cannot represent.GitHub issue: #17536
-
Definition import now rejects a binding with an unrecognised
destination_type.GitHub issue: #17587
-
AMQP 0-9-1 content headers are validated more strictly.
GitHub issue: #17697
Enhancements
-
ssl_options.supported_groupscan now be used inrabbitmq.confto restrict
the named groups offered for TLS 1.3 key exchange.GitHub issue: #17555
CLI Tools
Enhancements
-
CLI commands that accept sensitive values as interactive input now suppress terminal echoing
where possible. This behavior is specific to Erlang 28 and 29.GitHub issue: #17585
Management Plugin
Bug Fixes
-
Pagination bug fixes for stream connections.
-
A
404for a virtual host the user has no permissions on is now identical to the404for
a virtual host that does not exist.GitHub issue: #17540
-
The OAuth 2 token proxy responded with a
500to some malformed JSON documents.GitHub issue: #17646
-
The default
Content-Security-Policyvalue now includesbase-uri 'none'.GitHub issue: #17615
Enhancements
-
AMQP 1.0 consumers now link directly to their connection in the management UI.
Shovel Plugin
Bug Fixes
-
When the destination rejects a message, for example because the destination queue
hasx-overflowset toreject-publishand has reached its maximum length, the shovel
now returns the message to the source queue as a failed delivery. A quorum source queue
therefore dead-letters the message once it exceeds the delivery limit,
instead of redelivering it to the shovel over and over (a regression in4.3.0).With an AMQP 1.0 source, such a message used to be dead-lettered on the first rejection.
Now this happens once it exceeds the delivery limit. A classic source queue has no
delivery limit, so the message is returned to it until the destination accepts it.GitHub issue: #17794
-
A shovel with an AMQP 1.0 destination did not settle a message at the source when
the destination rejected or released it, and eventually stopped forwarding messages.GitHub issue: #17794
-
A shovel with an AMQP 1.0 source could restart and forward some messages twice when
the destination confirmed messages out of order.GitHub issue: #17794
-
A shovel with an AMQP 1.0 source could settle messages incorrectly after more than
4 billion deliveries. With a local destination, it could acknowledge a message at the
source before the destination confirmed it.GitHub issue: #17794
-
The AMQP 0-9-1 shovel now ignores publisher confirms for unknown delivery tags.
Federation Plugins
Bug Fixes
-
Federation links now ignore publisher confirms for unknown delivery tags.
-
An exchange federation link now handles
amqp_connection:open_channel/1returningclosing
instead of{error, Reason}.GitHub issue: #17655
MQTT Plugin
Bug Fixes
-
QoS 0 consumer queue deletion now retries in more scenarios.
GitHub issue: #17515
JMS Topic Exchange Plugin
Bug Fixes
-
Message selectors with arithmetic expressions now validate numerical arguments more thoroughly.
GitHub issue: #17613
Erlang AMQP 0-9-1 Client
Enhancements
-
The client now responds to a server-sent
basic.cancelwithbasic.cancel-okonly when the server
advertises support for it.GitHub issue: #17734
-
The
auth_mechanismquery parameter of an AMQP 0-9-1 URI is now restricted to
the mechanisms the client actually supports (plain,amqplain,external,
crdemo), and an unsupported value is now rejected when the URI is parsed
rather than when the connection is established. This also applies to the
Shovel and federation plugins, which parse URIs the same way.GitHub issue: #17466
-
Likewise, the
verifyquery parameter of an AMQP 0-9-1 URI now only accepts
verify_peerorverify_none, and an unsupported value is rejected when the
URI is parsed rather than when the TLS connection is established.GitHub issue: #17466
Erlang AMQP 1.0 Client
Enhancements
-
Connection configuration now accepts a
connect_timeout, applied to the socket
connect and, for TLS-enabled connections, to the TLS handshake as well.Contributed by @arrangabriel.
Dependency Changes
AI summary AMQP 1.0 headers parsing removed
RabbitMQ 4.4.0 is a new feature release.
Breaking Changes and Compatibility Notes
-
The following AMQP 0-9-1 headers are no longer parsed:
x-amqp-1.0-properties x-amqp-1.0-app-properties x-amqp-1.0-message-annotations x-amqp-1.0-footerRabbitMQ 3.13 and earlier used them to carry the AMQP 1.0 sections of a
message received over AMQP 1.0. Nothing has written them since 4.0, so only
a message stored by a 3.13 or earlier node and not read since carries them.
Such a message is still delivered, with these headers converted like any
otherx-header rather than restored as AMQP 1.0 sections. -
Likewise, the
x-basic-delivery-mode,x-basic-priorityand
x-basic-expirationmessage annotations are no longer parsed. They were
written before 4.0 when an AMQP 0-9-1 message was encoded as AMQP 1.0 for a
stream, so only a stream entry written by a 3.13 or earlier node carries
them, and reading it no longer restores those three properties. -
OpenID Connect discovery responses are now validated more strictly. A
deployment whose identity provider serves non-HTTPS (http://) endpoints,
or whoseissuerclaim does not match the discovery endpoint used to
retrieve it, will fail discovery validation after the upgrade.This is known to affect Cloud Foundry UAA, whose issuer is its token endpoint URL
rather than a prefix of its discovery endpoint.Set
auth_oauth2.discovery.verify_issuerand/or
auth_oauth2.discovery.verify_https_endpointstofalsebefore upgrading
installations with non-compliant IdPs such as Cloud Foundry UAA.See Discovery Payload Validation
for details on validation rules and configuration options. -
GET /api/auth/hash_password/{password}was replaced with another endpoint,POST /api/auth/hash_password.
The new endpoint consumes a POST body with JSON document with one key{"password": "..."}
Changes Worth Mentioning
Core Server
Enhancements
-
This version fully supports Erlang 28 and 29 series for both new clusters
and rolling upgrade scenarios. -
Quorum queues now support delayed messages.
A message with an
x-opt-delivery-timeannotation or header set to a future time,
in milliseconds since the Unix epoch, is routed and enqueued immediately but only
delivered to consumers once that time is reached.AMQP 1.0 clients set it as a message annotation, AMQP 0-9-1 clients as a
longheader.An AMQP 1.0 consumer can also delay redelivery of a message by setting
x-opt-delivery-timein the annotations of amodifiedoutcome.GitHub issue: #16583
-
AMQP 1.0 clients can now request sole (exclusive) ownership of a container ID.
In case of a conflict, the server either refuses the new connection or closes the existing one,
depending on what the client requested, per the AMQP 1.0 Connection Uniqueness
protocol extension.GitHub issue: #16669
-
A new, optional
x-name-prefixqueue argument sets the prefix used for a server-named
queue's generated name, capped at 64 bytes. The default prefix remains
amq.gen.This feature is specific to AMQP 0-9-1.
GitHub issue: #16233
-
The classic queue shared message store gained a new v2 on-disk file format (
.sqs).
New files are written in v2 automatically. Existing v1 files (.rdq) are left as-is.Note that a node with v2 files present cannot be downgraded to
4.3.xor earlier.GitHub issue: #17166
-
Classic queues now perform compaction more efficiently.
GitHub issue: #16194
-
x-modulus-hashexchange routing is now stable: assuming a topology that does not change,
messages carrying the same routing key are now routed to the same bound destination.Note: the exchange type has been moved from
rabbitmq_shardingto the core, so it is
now available even when said plugin is not enabled.GitHub issue: #15849
-
A change to the
delivery-limitpolicy key now takes effect for existing quorum queues.Previously the delivery limit could not be updated from a policy. Now quorum queues
reconfigure theirdelivery-limitvalue when a policy is added or updated.When the policy is removed the queue goes back to the default limit (
20).A negative policy value means "no limit".
GitHub issue: #16035
-
A passive declaration of a queue or an exchange (a check that it exists) requires any one of
theconfigure,writeorreadpermissions on that queue or exchange.This applies to
queue.declareandexchange.declarewithpassiveset totruein
AMQP 0-9-1, and to queue lookups in AMQP 1.0 management.GitHub issue: #16272
-
Reduce boot time of blank (brand new) nodes.
GitHub issue: #16479
-
Encrypted value support
for thedefinitions.https.urlkey inrabbitmq.conf.GitHub issue: #16632
-
Password salts for internal users are now generated using a cryptographically secure
pseudorandom number generator (CPRNG).GitHub issue: #16775
-
A topic exchange binding key can now contain at most two multi-segment (
#) wildcards.GitHub issue: #17039
-
Redeclaring a stream with an
x-max-agevalue that is equal to the existing one but written in
different units, for example1Das24h, is no longer rejected as having non-equivalent arguments. -
A stream can now start at an offset other than
0, set with the new
x-stream-initial-offsetoptional queue argument. While the stream is empty,
thefirstandnextoffset specifications resolve to this offset. The stream
protocol accepts the same value as thestream-initial-offsetargument of the
Createcommand.The initial offset is fixed when the stream is created, so there is no policy
for it, and redeclaring the stream with a different value is rejected.GitHub issue: #17300
-
Multiple stream coordinator efficiency improvements.
For example, the stream coordinator now retries failed stream member actions sooner, with
keeping a related stream partition process blocked for the retry delay.Failed operations are now retried after a short randomised delay, and actions that
failed because a node was down are retried when that node comes back.GitHub issue: #16515
-
Certain classic queue recovery scenarios now avoid a counterproductive timeout of 60s.
GitHub issue: #17733
-
Reduce CPU use of mostly idle quorum queues that do not have any queue decorators configured
(which is the common, baseline case). -
PBKDF2-HMAC-SHA256 now can be used for password hashing:
password_hashing_module = rabbit_password_hashing_pbkdf2_sha256GitHub issue: #17316
-
AMQP listeners can now bind to a Unix domain socket, using the same
listeners.tcp.*
settings as a TCP listener:listeners.tcp.1 = unix:/var/run/rabbitmq/rabbitmq.sock:0GitHub issue: #16963
-
connection_maxandchannel_maxwere renamed tomax_connectionsandmax_channels,
respectively, inrabbitmq.conf. The original names are still supported.GitHub issue: #16347
-
Messages are now converted from AMQP 0-9-1 to
AMQP 1.0 as a single data section, unless its payload consists of valid AMQP 1.0 body sections.An
expirationvalue that cannot be parsed is now ignored during that conversion.GitHub issue: #17272
-
Client connection listener startup now can be delayed by a configurable number of seconds
(default: no additional delay):listeners.startup_delay = 10 -
Internal peer discovery improvements.
GitHub issue: #17450
Bug Fixes
-
The stream coordinator could leave a stream without a writer and never recover it,
keep a stalestartaction after a leader election, or leave a replica
disconnected after its node came back.GitHub issue: #16515
-
Multiple bug fixes and optimizations to Single Active Consumers on streams.
-
AMQP 1.0: link handle uniqueness is now enforced per the protocol spec.
GitHub issue: #15780
-
Fix an issue that could trip an upgrade from
3.13to4.2and then immediately to4.3.GitHub issue: #16990
-
Upgrade safety improvements in mixed-version clusters (during rolling upgrades).
GitHub issue: #17128
-
Several bug fixes around binding deletion.
-
Quorum queue Continuous Membership Reconciliation (CMR)
could add more members (replicas) than the configured limit. -
Fixed an off-by-one issue in classic queue shared message store after an unclean shutdown.
GitHub issue: #17351
-
Routing to queues now handles concurrent queue deletion gracefully in more places, avoiding
confusing (and also non-actionable) exceptions.GitHub issue: #17664
-
The
basic.cancelnotification sent on a consumer delivery timeout
now properly clears consumer state even if the client does not respond withbasic.cancel-ok.GitHub issue: #17734
CLI Tools
Enhancements
-
Two new commands,
rabbitmqctl sole_connection_statusand
rabbitmqctl sole_connection_force_delete, inspect and manage AMQP 1.0 sole connections.GitHub issue: #16669
-
CLI commands that accept sensitive values as interactive input now suppress terminal echoing
where possible. This behavior is specific to Erlang 28 and 29.GitHub issue: #17585
Stream Plugin
Enhancements
-
stream.max_connectionsis a newrabbitmq.confsetting that limits the concurrent
number of RabbitMQ Stream Protocol client connections.GitHub issue: #16347
-
stream.max_super_stream_partitionsis a newrabbitmq.confsetting that limits the number of
partitions a super stream can have.GitHub issue: #16689
Management Plugin
Enhancements
-
A new endpoint,
GET /api/init, cuts the number of blocking requests the UI
has to make with certain authentication and login flows.GitHub issue: #17287
-
The
Referrer-Policyresponse header value of the HTTP API and the UI can now be configured
using themanagement.headers.referrer_policykey.GitHub issue: #16893
-
Support for multiple listeners for all HTTP-based protocols and the HTTP API.
Bug Fixes
-
The HTTP API did not return the status of blocked consumers.
GitHub issue: #16532
MQTT Plugin
Enhancements
-
mqtt.max_connectionsis a newrabbitmq.confsetting that limits the concurrent
number of MQTT client connections.GitHub issue: #16367
-
MQTT 5.0: a
Receive Maximumvalue of0is now rejected per the protocol spec.GitHub issue: #17057
-
The MQTT retained message store now has per-virtual host limits on the number of retained
messages and their total size. A message that would exceed either limit is not retained.The defaults are 100,000 messages and 1 GiB. Both can be changed, or set to
infinity:mqtt.retained_message_store.max_messages = 100000 mqtt.retained_message_store.max_size_bytes = 1073741824
GitHub issue: #17189
STOMP Plugin
Enhancements
-
Following the footsteps of AMQP 1.0 and MQTT in previous years,
the STOMP is now a standardlone protocol, that is, it is no longer built on AMQP 0-9-1.GitHub issue: #9141
-
stomp.max_connectionsis a newrabbitmq.confsetting that limits the concurrent
number of STOMP client connections.
GitHub issue: #16368
Web MQTT Plugin
Enhancements
-
The
Strict-Transport-Security(HSTS) header value can now be configured
using theweb_mqtt.hsts.policykey:web_mqtt.hsts.policy = max-age=31536000; includeSubDomains
GitHub issue: #16772
-
A new
web_mqtt.strict_origin_validationconfiguration key makes the plugin reject a WebSocket upgrade
request without anOriginheader whenweb_mqtt.allow_originsrestricts the allowed origins.web_mqtt.allow_originsalso accepts a new value,same_origin, which only allows requests whose
Originmatches the origin of the request itself:web_mqtt.allow_origins = same_origin web_mqtt.strict_origin_validation = true
GitHub issue: #16813
Web STOMP Plugin
Enhancements
-
The
Strict-Transport-Security(HSTS) header value can now be configured
using theweb_stomp.hsts.policykey:web_stomp.hsts.policy = max-age=31536000; includeSubDomains
GitHub issue: #16772
-
A new
web_stomp.strict_origin_validationconfiguration key makes the plugin reject a WebSocket upgrade
request without anOriginheader whenweb_stomp.allow_originsrestricts the allowed origins.web_stomp.allow_originsalso accepts a new value,same_origin, which only allows requests whose
Originmatches the origin of the request itself:web_stomp.allow_origins = same_origin web_stomp.strict_origin_validation = true
GitHub issue: #16813
Auth Backend OAuth 2 Plugin
Enhancements
-
OpenID Connect discovery responses fetched from identity providers are now
validated according to OpenID Connect Discovery 1.0 spec seciton §4.3. See
Discovery Payload Validation
for details on validation rules and configuration options.GitHub issue: #17363
-
OAuth 2.0 scopes now ca be extracted using regular expressions.
GitHub issue: #16196
Auth Backend Cache Plugin
Bug Fixes
-
The cache was never hit when the same user reconnected with the same credentials.
On busy deployments this could put significant extra load on the upstream authentication
backend and its dependencies, for example, the LDAP backend and the LDAP server(s) it uses.
Consistent Hashing Exchange Plugin
Bug Fixes
-
Routing no longer fails when the header it hashes on holds an empty array.
GitHub issue: #17081
Federation Plugin
Bug Fixes
-
Under certain conditions, deleting a federated queue could modify an exchange with the same
name in the same virtual host.
Shovel Plugin
Bug Fixes
-
Deleting a shovel that was still in the
startingstate left its status behind instead of deleting it.GitHub issue: #16767
-
A local shovel with
src-delete-afterset could transfer more messages than the configured number.GitHub issue: #17209
-
When the destination rejects a message, for example because the destination queue
hasx-overflowset toreject-publishand has reached its maximum length, the shovel
now returns the message to the source queue as a failed delivery. A quorum source queue
therefore dead-letters the message once it exceeds the delivery limit,
instead of redelivering it to the shovel over and over (a regression in4.3.0).With an AMQP 1.0 source, such a message used to be dead-lettered on the first rejection.
Now this happens once it exceeds the delivery limit. A classic source queue has no
delivery limit, so the message is returned to it until the destination accepts it.GitHub issue: #17794
-
A shovel with an AMQP 1.0 destination did not settle a message at the source when
the destination rejected or released it, and eventually stopped forwarding messages.GitHub issue: #17794
-
A shovel with an AMQP 1.0 source could restart and forward some messages twice when
the destination confirmed messages out of order.GitHub issue: #17794
-
A shovel with an AMQP 1.0 source could settle messages incorrectly after more than
4 billion deliveries. With a local destination, it could acknowledge a message at the
source before the destination confirmed it.GitHub issue: #17794
Erlang AMQP 0-9-1 Client
Enhancements
-
The
auth_mechanismquery parameter of an AMQP 0-9-1 URI is now restricted to
the mechanisms the client actually supports (plain,amqplain,external,
crdemo), and an unsupported value is now rejected when the URI is parsed
rather than when the connection is established. This also applies to the
Shovel and federation plugins, which parse URIs the same way. -
Likewise, the
verifyquery parameter of an AMQP 0-9-1 URI now only accepts
verify_peerorverify_none, and an unsupported value is rejected when the
URI is parsed rather than when the TLS connection is established.
Erlang AMQP 1.0 Client
Enhancements
- Connection configuration now accepts a
connect_timeout, applied to the socket
connect and, for TLS, to the handshake as well. Without it, a peer that accepts the
TCP connection and then stops responding blocksamqp10_client_supindefinitely,
which in turn blocks every other connection attempt in the node.
Defaults are unchanged:infinityfor TCP and TLS, 5000 ms for WebSockets.
Dependency Changes
osiriswas upgraded to1.14.1rawas upgraded to3.2.0khepriwas upgraded to0.19.3portunuswas introduced at0.14.0thoaswas dropped: JSON encoding and decoding now uses the Erlang/OTPjsonmodule
Source Code Archives
To obtain source code of the entire distribution, please download the archive named rabbitmq-server-4.4.0.tar.xz
instead of the source tarball produced by GitHub.
RabbitMQ 4.3.6 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
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
-
Deleting an exchange did not delete the bindings that pointed to it as a destination.
A few related cases around auto-delete exchanges, transient queue cleanup and
virtual host deletion were fixed along the way. -
Quorum queue continuous membership reconciliation could add more replicas than
the configured target. -
Certain malformed
urn:uuid:correlation or message ID caused exceptions during message format conversion.
Such values are now rejected.GitHub issue: #17328
-
An operation that refers to an unknown queue type now fails with a
precondition_failedchannel exception instead of an exception and abrupt channel termination.GitHub issue: #17327
-
Classic queue recovery counted some message store references more than once.
GitHub issue: #17351
-
x-max-agevalues are now compared as durations, so redeclaring a stream
with1Dwhen it was declared with24hno longer fails with a
PRECONDITION_FAILED(non-equivalent argument) exception.With contributions from @Vishal-770.
-
AMQP 1.0 SQL filters: the value matched by a
LIKEpattern with several
wildcards is now bounded independently of the message size limit.GitHub issue: #17332
-
Direct connections (used by the shovel and federation plugins) now enforce
channel_max_per_node
the same way network connections do.Contributed by @Ayanda-D.
GitHub issue: #16610
Enhancements
-
New
rabbitmq.confsetting:channel_tx_message_max. It bounds the number of publishes a channel
buffers in an open AMQP 0-9-1 transaction, and defaults to 10,000. Going over the limit
results in aprecondition_failedchannel exception.Most applications won't be affected by this change and likely will not have to
increase the default limit.GitHub issue: #17331
-
New
rabbitmq.confsetting:listeners.startup_delay. It delays the start of client connection
listeners by the specified number of seconds, for environments where applications
begin connecting as soon as a port is open, before the node has finished booting.Contributed by @Vishal-770.
-
Several channel interceptors can now be registered for the same AMQP 0-9-1 operation,
as long as they use different priorities. Previously, if two enabled plugins intercepted
the same operation, for examplebasic.publish, channels could not be opened at all.Priorities are set per interceptor module in
rabbitmq.conf. Lower values run first,
and omitted interceptors are assumed to have the priority of0:channel_interceptor.priorities.rabbit_timestamp_interceptor = 1 channel_interceptor.priorities.rabbit_routing_node_stamp_interceptor = 2 channel_interceptor.priorities.rabbit_sharding_interceptor = 3
Contributed by @Ayanda-D.
GitHub issue: #17182
-
Shovels now support a new AMQP URI query parameter,
customize_hostname_check,
that controls how the target hostname is matched against the server certificate,
for example with wildcard certificates.Contributed by @jiangranwang.
GitHub issue: #17221
CLI Tools
Bug Fixes
-
rabbitmq-diagnostics check_certificate_expirationnow handles certificate files
that cannot be read, and certificates that use the RFC 5280UTCTimeformat,
the same way the HTTP API health check does.Contributed by @Vishal-770.
Enhancements
-
Two new commands,
rabbitmqctl list_channel_interceptorsand
rabbitmqctl set_channel_interceptor_priorities, list the active channel interceptors
and adjust their priorities at runtime. Priorities set this way are not persisted
and do not survive a node restart.Contributed by @Ayanda-D.
GitHub issue: #17182
Stream Plugin
Bug Fixes
-
During a rolling upgrade, a stream metadata request could leave out a peer node
that ran a different version.GitHub issue: #17333
Stream Management Plugin
Bug Fixes
-
The publishers and consumers listing now verifies virtual host access like
other comparable HTTP API endpoints.
Management Plugin
Bug Fixes
-
The channels list and individual channel pages now display basic information
when management statistics are disabled, instead of returning a400 Bad Request. -
Several HTTP API endpoints returned a
500instead of a400for invalid
range parameters or an invalid timeout header:GET /api/nodes/{node},
GET /api/healthchecks/node[/{node}],GET /api/federation-links,
GET /api/health/checks/alarmsandGET /api/health/checks/local-alarms. -
The certificate expiration health check no longer responds with a
500
for certificate files that cannot be read, or for certificates that use the
RFC 5280UTCTimeformat.Contributed by @Vishal-770.
-
Optional argument (
x-*) values are no longer coerced to strings in the management UI.GitHub issue: #17177
Enhancements
-
Consumers on protocols without channels (for example, AMQP 1.0 and MQTT)
now link directly to their connection in the management UI.Contributed by @vampirebyte.
GitHub issue: #17206
Shovel Plugin
Bug Fixes
-
Shovel types provided by plugins can now be used as
src-protocolanddest-protocolvalues. -
A local shovel with
src-delete-afterset to a number could in some cases
transfer more messages than that number.GitHub issue: #17209
MQTT Plugin
Enhancements
-
The retained message store now has per-virtual host limits on both the number of messages
and their total size:mqtt.retained_message_store.max_messages(defaults to 100000)
andmqtt.retained_message_store.max_size_bytes(defaults to 1 GiB).GitHub issue: #17189
STOMP Plugin
Bug Fixes
-
STOMP and Web STOMP connections now enforce credential expiry (for example, of OAuth 2 tokens)
the same way other protocols do.GitHub issue: #17244
Web MQTT and Web STOMP Plugins
Bug Fixes
-
web_mqtt.ssl.*andweb_stomp.ssl.*now accept more TLS keys inrabbitmq.conf,
includingverifyandfail_if_no_peer_cert.
LDAP AuthN and AuthZ Backend Plugin
Bug Fixes
-
DN escaping introduced in an earlier release was too strict for certain Active Directory
setups, for example when the client provides a full DN that contains a backslash.
Escaping is now applied to DN template values only. -
Active Directory down-level logon names (
DOMAIN\username) can be used to log in again.Contributed by @jiangranwang.
GitHub issue: #17220
Trust Store Plugin
Enhancements
-
The trust store now also covers the HTTP API, Web MQTT
and Web STOMP listeners.GitHub issue: #17303
Consul Peer Discovery Plugin
Bug Fixes
-
A
404response from the Consul API no longer stops node boot; peer discovery is retried instead.
Dependency Changes
RabbitMQ 4.3.5 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
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
-
With direct reply-to, a message routed to multiple
targets that resolved to the same process could be delivered to it more than once.GitHub issue: #17071
-
Quorum queue recovery from a recovery checkpoint could leave a part of the queue's
internal state only partially initialized.GitHub issue: #17012
-
In clusters that run a mix of
4.2.xand4.3.xnodes during a rolling upgrade,
local quorum queue queries now fall back to the previous state machine version
instead of failing.GitHub issue: #17128
-
A malformed AMQP 1.0 frame now results in a framing error returned to the client
instead of an exception.GitHub issue: #17101
-
The AMQP 1.0 message parser now validates message sections more strictly
and decodes certain types of arrays more efficiently.GitHub issue: #17049
-
Topic exchanges now limit the number of multi-segment (
#) wildcards a binding key
can use to two. The#wildcard is meant to be used as the final segment, that is, just once.GitHub issue: #17039
-
When connection credentials are refreshed (for example, when an OAuth 2 token
is renewed), the user's tags are now updated instead of being carried over from the
original state.GitHub issue: #17029
-
Definition import from an HTTPS endpoint
no longer fails when a password-protected TLS (HTTPS) client certificate is used.Contributed by @Pyolar.
GitHub issue: #16973
-
The AMQP 1.0 Erlang client no longer logs an exception when a link is already detached.
Workloads that use short lived links could produce a substantial amount of log noise.GitHub issue: #17124
Enhancements
-
Authentication events are now logged under a new logging category,
user.
Successful logins are logged at theinfolevel, failed login attempts at thewarninglevel.GitHub issue: #16907
CLI Tools
Enhancements
-
rabbitmqctl hash_passwordnow supports more password hashing functions.
Stream Plugin
Bug Fixes
-
A stream protocol connection can have at most 256 publishers and 256 subscriptions,
a limit that comes from the protocol's wire format. Attempts to go over these limits
are now rejected early with a clear error instead of failing later with an unrelated one.GitHub issue: #17123
Enhancements
-
Before a stream client connection completes authentication and authorization (that is, before
a successfulopen), the server now enforces a lowframe_maxceiling instead of
the full configured value. The default, 8192 bytes, is high enough to accommodate realistic
JWT tokens used with SASL PLAIN authentication,
and mirrors a mechanism already in place for AMQP 0-9-1 connections. It can be adjusted
with the newstream.initial_frame_maxsetting.GitHub issue: #17053
-
New setting:
stream.max_uncompressed_sub_entry_batch_size. It bounds the declared
uncompressed size of a published sub-entry batch, and defaults to 67108864 (64 MiB),
the same default already used by the Java client'smaxUncompressedSubEntryBatchSize.
The broker and any client publishing to it should be configured with the same value.GitHub issue: #17103
Management Plugin
Bug Fixes
-
HTTP API endpoints that accept a node name, including the federation and tracing related ones,
now validate that the target node is a cluster member. -
The management UI no longer displays certain alert messages twice.
GitHub issue: #17127
Enhancements
-
When
management.credential_encryption_secretis configured, the management UI login endpoint
(POST /api/login) returns client credentials encrypted usingAES-256-GCMwith a key
derived from the configured secret, and returns the ciphertext as an opaque token prefixed
withrmqe.. The browser stores this token and presents it on all subsequent requests
using theAuthorization: Bearer rmqe.<token>header.The secret MUST be identical on every node in the cluster.
Important: during a rolling cluster upgrade, enable this feature only after all nodes have been upgraded.
This is particularly important for clusters behind a load balancer: nodes that run older
versions will not recognize the encrypted tokens and will reject the requests,
unexpectedly logging users out.GitHub issue: #16705
-
GET /api/definitionsnow supports conditional requests (ETag).The
ETagvalue is derived from the metadata store Raft index, so the tag will
naturally change as the metadata store serves writes. -
The
Referrer-PolicyHTTP response header can now be configured with
themanagement.headers.referrer_policysetting.GitHub issue: #16893
-
When
management.http.hide_allow_headeris set totrue, theAllowHTTP response header
is omitted from all responses except405 Method Not Allowedones, where it is required
by the HTTP specification. This avoids disclosing the supported HTTP methods to clients.GitHub issue: #16893
-
When
management.definitions.require_json_extensionis set totrue, both the management UI
and the HTTP API will reject definition upload where the file does not have a.jsonextension.
The setting defaults tofalse. Regardless of this setting, the server always validates
that the uploaded content is valid JSON before importing it.GitHub issue: #16946
OAuth 2 AuthN and AuthZ Backend Plugin
Bug Fixes
-
When RabbitMQ is behind a proxy that terminates TLS, the OAuth 2 login flow
now honors theX-Forwarded-Proto,X-Forwarded-HostandX-Forwarded-Portheaders
when rewriting the token endpoint URL in the OpenID discovery payload.GitHub issue: #17153
Shovel Plugin
Bug Fixes
-
Reduced log noise.
GitHub issue: #17028
-
Static shovels that do not define any
declarationsfailed to start. -
When a topology setup failure stops a shovel worker, the specific reason is now
reported instead of a generic one.GitHub issue: #17135
-
The Shovel HTTP API now processes shovel URIs the same way the federation plugin
processes its upstream URIs.GitHub issue: #17134
Enhancements
-
Shovel TTL: dynamic shovels support a new setting,
src-delete-after-duration,
that instructs the shovel to self-delete after at least the specified duration.Contributed by @michalovits.
Federation Plugin
Bug Fixes
-
A malformed upstream URI could prevent a federation link from starting even when other,
well-formed URIs were available. All candidate URIs are now tried.Contributed by @sauravonwww.
GitHub issue: #17046
MQTT Plugin
Bug Fixes
-
Packets split across many network fragments are now parsed more efficiently.
GitHub issue: #17093
-
MQTT 5.0 properties are now parsed strictly: a property that is not valid
for a given packet type is rejected.GitHub issue: #17039
-
A
Receive Maximumvalue of 0, prohibited by the MQTT 5.0 specification, is now rejected.GitHub issue: #17035
STOMP Plugin
Bug Fixes
-
Frame size limits are now enforced earlier in the connection lifecycle.
GitHub issue: #17116
Web STOMP Plugin
Bug Fixes
-
The accumulated frame size is now checked against
max_frame_sizeafter a connection
has authenticated, matching the behavior of "regular" STOMP connections.GitHub issue: #17065
Consistent Hash Exchange Plugin
Bug Fixes
-
An edge case in bucket selection is now handled gracefully.
GitHub issue: #17081
Dependency Changes
RabbitMQ 4.3.4 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
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
-
Quorum queues in clusters upgraded from
3.13.xto4.2.xand then to4.3.xcould stop
emitting metrics and taking snapshots after a node restart. -
The AMQP 1.0 parser now detects standard message body sections more strictly.
GitHub issue: #17017
-
The AMQP 1.0 parser now decodes certain array values more efficiently.
GitHub issue: #16994
Stream Plugin
Bug Fixes
-
The single active consumer coordinator
did not notify a consumer that was re-selected for activation while it was still deactivating,
leaving the group without an active consumer.Contributed by @pterygota.
Management Plugin
Bug Fixes
-
Very short lived exclusive queues could cause an exception during metric collection, producing
log noise. -
After an IdP-initiated OAuth 2 login, the management UI now returns the user
to the page that was open before the login instead of the default one.Contributed by @thisisnsh.
-
Several security fixes and validation gaps were addressed:
- The HTTP API now returns 404 Not Found instead of 401 Unauthorized when a user lacks permission to a vhost, avoiding disclosure of the vhost's existence.
- Token expiry values that use a floating point number are now accepted, not just integers.
- To access all user-limits it is required administrator priviledge
- To access a user-limits for a specific user now require the requester to be that same user or have administrator/monitoring privileges.
GitHub issue: #16709
Enhancements
-
The management UI Content Security Policy (CSP) no longer includes the
unsafe-evaland
unsafe-inlinedirectives.GitHub issue: #16916
Federation Plugin
Bug Fixes
-
In scenarios that involved a federated queue and a federated exchange with exactly the same name in the same virtual host,
deleting an upstream unintentionally corrupted the federated exchange(s) operating state, breaking federation
for the exchange in question.
Dependency Changes
None in this release.
@ Every self-hosted release, weekly
One Monday email with the week's stable releases across the directory.
More in Message Broker
RedisRedis is a self-hosted, open-source in-memory data structure server used as a database, cache, message broker, and vector query engine with sub-millisecond latency.
ValkeySelf-hosted, open-source Valkey is an in-memory key-value database for caching, queues and primary data, with replication, Sentinel failover and cluster sharding.
activemqThe open-source, self-hosted Apache ActiveMQ message broker handles JMS, AMQP, MQTT, STOMP and REST traffic from Java, C, Python and .Net clients.
Apache KafkaApache Kafka is a self-hosted, open-source event streaming platform for high-performance data pipelines and mission-critical applications.
automqSelf-hosted, open-source Apache Kafka fork with stateless brokers that store logs on S3 or MinIO and rebalance partitions in seconds.
beanstalkdbeanstalkd is a self-hosted, open-source work queue: a small C daemon where producers put jobs into named tubes and workers reserve, bury or kick them over plain TCP.
BunkerMBunkerM is a self-hosted, open-source MQTT platform bundling Eclipse Mosquitto with a web dashboard, ACL management, message history, anomaly detection, and AI.
Eclipse MosquittoSelf-hosted open-source MQTT broker for MQTT 5.0, 3.1.1 and 3.1 with TLS, WebSockets, bridging, ACLs and a C client library plus CLI pub/sub tools.
forqForq is a self-hosted, open-source message queue on SQLite running as a single binary or Docker container with admin UI, metrics, DLQ, and SDKs.
gearmandGearman is a self-hosted, open-source job server for parallel processing, load balancing, and cross-language function calls.
HiveMQ Community EditionHiveMQ Community Edition is an open-source Java MQTT broker with full MQTT 3.x and MQTT 5 support, TLS and WebSocket listeners, a Java extension SDK and an embedded mode.
logging-flumeOpen-source, self-hosted ingestion service from Apache: streaming agents with sources, channels and sinks move large amounts of log data to HDFS, Kafka or HBase.
0 comments