We are pleased to announce version 3.0 of RabbitMQ!
This release introduces dynamic, policy-based control of mirroring and federation, improves the user friendliness of clustering, adds support for per-message TTL, introduces plugins for web-STOMP and MQTT, and adds many smaller new features and bug fixes.
Binary and source distributions of the new release can be found on the download page
To implement some of these features, a few things changed and may require attention in an upgrade. This blog post explains why things changed and what to do about them. You can read about all the bug fixes, the key high level changes are listed below:
- Queue mirroring is no longer controlled by the
x-ha-policyargument when declaring a queue. Your applications can continue to declare this argument, but it won’t cause queues to be mirrored. Instead you can declare one or more policies which control which queues are mirrored, and how.
- Federation is configured quite differently in RabbitMQ 3.0. The
x-federationexchange type no longer exists; instead normal exchanges are made federated by policy in the same way that HA queues are. Furthermore, upstreams are defined dynamically as well.
- The clustering-setup commands in rabbitmqctl have changed.
- The RabbitMQ server now disconnects clients which send frames larger than the negotiated
frame_maxsetting for the connection.
- The management plugin now listens on port 15672, not 55672. JSON-RPC channel now listens on 15670, not 55670.
|>> You can learn more at the RabbitMQ Resources page or website. As always, we appreciate questions, bug reports, feedback, and suggestions at the RabbitMQ discussion list.