release-notes/4.3.4.md
RabbitMQ 4.3.4 is a maintenance release in the 4.3.x release series.
It is strongly recommended that you read 4.3.0 release notes
in detail if upgrading from a version prior to 4.3.0.
The minimum supported Erlang version for this release series is 27.0.
RabbitMQ and Erlang/OTP Compatibility Matrix has more details on Erlang version requirements for RabbitMQ.
Nodes will fail to start on older Erlang releases.
Release notes can be found on GitHub at rabbitmq-server/release-notes.
Quorum queues in clusters upgraded from 3.13.x to 4.2.x and then to 4.3.x could stop
emitting metrics and taking snapshots after a node restart.
The AMQP 1.0 parser now detects standard message body sections more strictly.
GitHub issue: #17017
The AMQP 1.0 parser now decodes certain array values more efficiently.
GitHub issue: #16994
The single active consumer coordinator did not notify a consumer that was re-selected for activation while it was still deactivating, leaving the group without an active consumer.
Contributed by @pterygota.
Very short lived exclusive queues could cause an exception during metric collection, producing log noise.
After an IdP-initiated OAuth 2 login, the management UI now returns the user to the page that was open before the login instead of the default one.
Contributed by @thisisnsh.
The management UI Content Security Policy (CSP) no longer includes the unsafe-eval and
unsafe-inline directives.
GitHub issue: #16916
In scenarios that involved a federated queue and a federated exchange with exactly the same name in the same virtual host, deleting an upstream unintentionally corrupted the federated exchange(s) operating state, breaking federation for the exchange in question.
None in this release.