root
/
rabbitmq-server
mirror of https://github.com/rabbitmq/rabbitmq-server.git
1
0
Fork 0
Code Issues Actions 8 Packages Projects Releases Wiki Activity

4.0.1 release notes: wording

This commit is contained in:
Michael Klishin 2024-10-09 11:54:26 -04:00
parent 9893a2bd48
commit 2eeac4ba59
No known key found for this signature in database
GPG Key ID: FF4F6501646A9C9A
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
release-notes/4.0.1.md
View File

@ -70,13 +70,14 @@ accidentally sacrificed.
### AMQP 0.9.1 x-death header ### AMQP 0.9.1 x-death header
Up to RabbitMQ 3.13, when an AMQP 0.9.1 client (re-)published a message to RabbitMQ, RabbitMQ interpreted the Up to RabbitMQ 3.13, when an AMQP 0.9.1 client (re-)published a message to RabbitMQ, RabbitMQ interpreted the
AMQP 0.9.1 [x-death](https://www.rabbitmq.com/docs/dlx#effects) header in the published message's `basic_message.content.properties.headers` field. AMQP 0.9.1 [`x-death`](https://www.rabbitmq.com/docs/dlx#effects) header in the published message's `basic_message.content.properties.headers` field.
RabbitMQ 4.x will not interpret this `x-death` header anymore when clients (re-)publish a message. RabbitMQ 4.x will not interpret this `x-death` header anymore when clients (re-)publish a message.
Note that RabbitMQ 4.x will continue to set and update the `x-death` header every time a message is dead-lettered, including when a client **rejects** the message. Note that RabbitMQ 4.x will continue to set and update the `x-death` header every time a message is dead-lettered, including when a client **rejects** the message.
If you have a use case where you relied on RabbitMQ incrementing the `count` fields within the `x-death` header array elements for new messages **(re-)published** Applications that rely on RabbitMQ incrementing the `count` fields within the `x-death` header array elements for new messages **(re-)published**
(instead of existing messages being rejected), consider introducing and incrementing [your own custom non `x-` header](https://github.com/rabbitmq/rabbitmq-server/issues/10709#issuecomment-1997083246) instead. (instead of existing messages being rejected), should introduce and increment [a separate `x-` header](https://github.com/rabbitmq/rabbitmq-server/issues/10709#issuecomment-1997083246),
with a name that would not be updated by RabbitMQ itself.
### CQv1 Storage Implementation was Removed ### CQv1 Storage Implementation was Removed