|
| 1 | +## RabbitMQ 4.1.5 |
| 2 | + |
| 3 | +RabbitMQ `4.1.5` is a maintenance release in the `4.1.x` [release series](https://www.rabbitmq.com/release-information). |
| 4 | + |
| 5 | +It is **strongly recommended** that you read [4.1.0 release notes](https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.1.0) |
| 6 | +in detail if upgrading from a version prior to `4.1.0`. |
| 7 | + |
| 8 | + |
| 9 | +### Minimum Supported Erlang Version |
| 10 | + |
| 11 | +[RabbitMQ and Erlang/OTP Compatibility Matrix](https://www.rabbitmq.com/docs/which-erlang) has more details on Erlang version requirements for RabbitMQ. |
| 12 | + |
| 13 | +Nodes **will fail to start** on older Erlang releases. |
| 14 | + |
| 15 | + |
| 16 | +## Changes Worth Mentioning |
| 17 | + |
| 18 | +Release notes can be found on GitHub at [rabbitmq-server/release-notes](https://github.com/rabbitmq/rabbitmq-server/tree/v4.1.x/release-notes). |
| 19 | + |
| 20 | + |
| 21 | +### Core Server |
| 22 | + |
| 23 | +#### Bug Fixes |
| 24 | + |
| 25 | + * Classic queues could run into a rare message store exception that resuulted in |
| 26 | + a loss of a few messages. |
| 27 | + |
| 28 | + Special kudos to the contributors who have spent a very significant amount of time |
| 29 | + reproducing and debugging the issue: @lhoguin @lukebakken @trvrnrth @gomoripeti |
| 30 | + |
| 31 | + GitHub issues: [#14181](https://github.com/rabbitmq/rabbitmq-server/discussions/14181), [#14576](https://github.com/rabbitmq/rabbitmq-server/pull/14576) |
| 32 | + |
| 33 | + * Messages routed to quorum queues during or immediately before a network partition, |
| 34 | + in some cases were not re-republished internally in certain cases. |
| 35 | + |
| 36 | + GitHub issue: [#14589](https://github.com/rabbitmq/rabbitmq-server/pull/14589) |
| 37 | + |
| 38 | + * Quorum queues with disabled [poison message handling](https://www.rabbitmq.com/docs/quorum-queues#poison-message-handling) |
| 39 | + (an unlimited number of redeliveries, which is **not** a recommended practice) could accumulate |
| 40 | + a significant number of Raft log segment files. |
| 41 | + |
| 42 | + GitHub issues: [#14202](https://github.com/rabbitmq/rabbitmq-server/issues/14202), [#14458](https://github.com/rabbitmq/rabbitmq-server/pull/14458) |
| 43 | + |
| 44 | +### Streams |
| 45 | + |
| 46 | +#### Bug Fixes |
| 47 | + |
| 48 | + * Streams declaration response was missing a leader field when the stream was declared via AMQP 1.0 or 0.9.1 |
| 49 | + (that is, not the RabbitMQ Stream Protocol). |
| 50 | + |
| 51 | + GitHub issue: [#14476](https://github.com/rabbitmq/rabbitmq-server/pull/14476) |
| 52 | + |
| 53 | +### CLI Tools |
| 54 | + |
| 55 | +#### Bug Fixes |
| 56 | + |
| 57 | + * Fixes JSON formatting of cluster nodes produced by `rabbitmq-diagnostics status --formatter json` |
| 58 | + |
| 59 | + GitHub issue: [#14509](https://github.com/rabbitmq/rabbitmq-server/issues/14509) |
| 60 | + |
| 61 | +### Shovel Prometheus Plugin |
| 62 | + |
| 63 | +#### Bug Fixes |
| 64 | + |
| 65 | + * Requesting shovel status via Prometheus at a specific moment resulted in an exception |
| 66 | + because the plugin did not consider a highly transient starting state. |
| 67 | + |
| 68 | + GitHub issue: [#14481](https://github.com/rabbitmq/rabbitmq-server/pull/14481) |
0 commit comments