| RabbitMq | Minimum required Erlang/OTP | Maximum supported Erlang/OTP | Notes |
|---|
| 3.7.7 |
|
|
- RabbitMQ 3.7.7 is the first version to support Erlang/OTP 21
- Erlang/OTP 21 includes file I/O efficiency improvements
- For the best TLS support, the latest version of Erlang/OTP 21.0.x is recommended
- Versions prior to 19.3.6.4 have known bugs (e.g. ERL-430, ERL-448) that can prevent RabbitMQ nodes from accepting connections (including from CLI tools) and stopping
- Versions prior to 19.3.6.4 are vulnerable to the ROBOT attack (CVE-2017-1000385)
- On Windows, Erlang/OTP 20.2 changed default cookie file location
|
| |
|
|
- For the best TLS support, the latest version of Erlang/OTP 20.3.x is recommended
- We recommend Erlang/OTP 19.3.6.4 or later, earlier versions have known bugs (e.g. ERL-430, ERL-448) that can prevent RabbitMQ nodes from accepting connections (including from CLI tools) and stopping
- Versions prior to 19.3.6.4 are vulnerable to the ROBOT attack (CVE-2017-1000385)
- On Windows, Erlang/OTP 20.2 changed default cookie file location
|
| |
|
|
|
| |
|
|
- For the best TLS support, the latest version of Erlang/OTP 20.1.x is recommended
- We recommend Erlang/OTP 19.3.6.4 or later, earlier versions have known bugs (e.g. ERL-430, ERL-448) that can prevent RabbitMQ nodes from accepting connections (including from CLI tools) and stopping
- Versions prior to 19.3.6.4 are vulnerable to the ROBOT attack (CVE-2017-1000385)
|
| |
|
|
- For the best TLS support, the latest version of Erlang/OTP 19.3.x is recommended
- We recommend Erlang/OTP 19.3.6.4 or later, earlier versions have known bugs (e.g. ERL-430, ERL-448) that can prevent RabbitMQ nodes from accepting connections (including from CLI tools) and stopping
- Versions prior to 19.3.6.4 are vulnerable to the ROBOT attack (CVE-2017-1000385)
|
| |
|
|
- Erlang 18.x versions have known bugs (e.g. ERL-430, ERL-448) that can prevent RabbitMQ nodes from accepting connections (including from CLI tools) and stopping
- All Erlang versions supported by these releases are vulnerable to the ROBOT attack (CVE-2017-1000385)
|
| |
|
|
- RabbitMQ 3.5 was released 2015-03-11, and reached end of life 2017-09-11, we strongly discourage its use
|
| |
|
|
- RabbitMQ 3.4 was released 2014-10-21, and reached end of life 2017-05-31, we strongly discourage its use
|
