RabbitMQ 4.0.6 is
a new patch release in the 4.0.x series.
This series is currently covered by community support.
Release artifacts can be obtained on GitHub as well as RPM, Debian package repositories.
If upgrading from a version prior to 4.0, please consult
the 4.0 release notes.
RabbitMQ 3.13.8 is a new patch release in the 3.13.x series.
This series is currently covered by commercial support only.
For publicly available open source releases, see the 4.0.x series.
Release artifacts for the 3.13.x series can be obtained via the Broadcom customer portal.
If upgrading from a version prior to 3.13.9, please consult the 3.13.0 release notes.
Tanzu RabbitMQ 3.13.8 is a new patch release in the 3.13.x series of
the commercial edition of RabbitMQ.
This edition includes additional feature such as Warm Standby Replication, intra-cluster traffic compression and a FIPS-enabled Erlang runtime.
Tanzu RabbitMQ is available on Kubernetes, as an OCI image, and an OVA image.
This release is based on open source RabbitMQ 3.13.x and includes all the latest backports
in open source RabbitMQ 3.13.8.
Release artifacts for the 3.13.x series can be obtained via the Broadcom customer portal:
If upgrading from a version prior to 3.13.9, please first consult the open source RabbitMQ 3.13.0 release notes.
It's time to retire the myth that RabbitMQ stores messages in memory. While it was true in the early days of RabbitMQ, and an option for the last 10 years, modern RabbitMQ versions almost always write messages to disk right away. In this blog post we review how different queue types store messages but the short answer is: not in memory!
The Erlang Port Mapper Daemon (epmd) is a built-in component that helps Erlang-based applications (including RabbitMQ) discover each other’s distribution ports.
Together with DNS for hostname resolution, epmd is a piece of infrastructure RabbitMQ nodes rely on for clustering, inter-node communication
and CLI tools connectivity.
While epm is very limited in scope, its exposure to the public Internet often means that Erlang distribution ports are also exposed.
This creates a potential security risk: if attackers find these distribution ports, they'd be one secret value away from being able to run
CLI commands against the node (or cluster).
Recent scans have revealed over 85,000 instances of publicly accessible epmd, with roughly half associated with RabbitMQ servers.
Fortunately, all it usually takes to mitigate this risk is limiting network access to a range of ports. epmd and inter-node communication
can also be limited to local network interfaces, in particular for single node clusters used for running tests.
Read the full article on the Erlang Ecosystem Foundation blog.
RabbitMQ 4.0.5 is
a new patch release in the 4.0.x series.
This series is currently covered by community support.
Release artifacts can be obtained on GitHub as well as RPM, Debian package repositories.
If upgrading from a version prior to 4.0, please consult
the 4.0 release notes.
RabbitMQ 4.1 introduces an exciting new feature: AMQP filter expressions for streams.
This feature enables RabbitMQ to support multiple concurrent clients, each consuming only a specific subset of messages while preserving message order. Additionally, it minimizes network traffic between RabbitMQ and its clients by dispatching only the messages that match the clients' interests.
In this blog post, we’ll explore what AMQP filter expressions are and walk through a simple Java example of how to use them.
This blog post explores use cases of the AMQP 1.0 modified outcome.
This blog post outlines ten advantages of AMQP 1.0 flow control over AMQP 0.9.1, supported by two benchmarks demonstrating significant performance gains. Additionally, we delve into the powerful AMQP 1.0 flow control primitives and how they are used in RabbitMQ.
RabbitMQ 4.0 (currently in beta) includes new quorum queue features: