release-notes/3.9.3.md
RabbitMQ 3.9.3 is a maintenance release in the 3.9.x release series that addresses a regression introduced in 3.9.0.
All users are recommended to upgrade to this release.
This is what changed since v3.9.2.
Please refer to the Upgrading to 3.9 section from v3.9.0 release notes if you are upgrading from a version prior to 3.9.0.
This release requires at least Erlang 23.2, and supports the latest Erlang 24 version, 24.0.5 at the time of release. RabbitMQ and Erlang/OTP Compatibility Matrix has more details on Erlang version requirements for RabbitMQ.
Release notes are kept under rabbitmq-server/release-notes. Contributors are encouraged to update them together with their changes. This helps with release automation and more consistent release schedule.
Queues that had messages with per-message TTL in them could fail to recover their indices after a restart.
JSON logging could fail with an exception when a logged event included epoch-based timestamp value.
GitHub issue: #3281
JSON logging now uses integers (as opposed to floats) to represent epoch-based timestamps
GitHub issue: #3282
RabbitMQ application no longer reports the stopping event to systemd. This was counterproductive when the application was stopped but the runtime (Erlang VM) was kept running,
e.g. via rabbitmqctl stop_app or by the pause minority partition handling strategy.
Now systemd service monitoring will recognize a node as stopped only when the runtime is stopped, which is usually the behavior operators expect.
No dependency changes in this release.
To obtain source code of the entire distribution, please download the archive named rabbitmq-server-3.9.3.tar.xz instead of the source tarball produced by GitHub.