RabbitMQ 3.7.8 RC3 releases: open source message broker
RabbitMQ is the most popular open source message broker.
RabbitMQ is lightweight and easy to deploy on-premises and in the cloud. It supports multiple messaging protocols. RabbitMQ can be deployed in distributed and federated configurations to meet high-scale, high-availability requirements.
RabbitMQ runs on many operating systems and cloud environments and provides a wide range of developer tools for most popular languages.
Enterprise & Cloud Ready
Tools & Plugins
Management & Monitoring
HTTP-API, command line tool, and UI for managing and monitoringRabbitMQ.
RabbitMQ 3.7.8 RC3 releases.
- Virtual host (specifically binding) recovery has been optimized.
- A queue sync operation now can becancelledwhen a resource alarm is in effect on the receiving node.
- Inter-node communication port (a.k.a. distribution port) unintentionally used an excessively large
buffer size (1.2 GB instead of 128 MB). Kudos to Chris Friesen for noticing and reporting this.
- A resource alarm triggered during boot could preventnodefrom starting.
- Syslog configuration parameters could be rejected by config validator.
- On Erlang/OTP 21 Syslog server now can be configured using a hostname (not just an IP address).
rabbitmqctl rename_cluster_nodedocumentation improvements.
- Policies were unintentionally excludedfrom
- Virtual host imported from definitions or created via HTTP API will explicitlyawaitfor thevhosttoinitialise
on all cluster nodes. This change was previously scheduled for
3.7.6but was only partially applied (didn’t have
any effect on HTTP API clients).
- HTTP API connection endpoints returned a duplicate key,
- Cowboy timeouts now can be configured.
rabbitmqadminnow supports a new argument,
- Switching sections will now scroll to the top of the newly rendered page.
- Nodes experiencing very high connection churn could run out of Erlang processes.
- Improved OTPreleasehandling compatibility.
- Link initialization optimizations.
- It is now possible to set up a tracer on any cluster node via management UI and HTTP API.
- Tracer connection credentials now can be specified via the management UI and HTTP API.