From c458cba92303b21ee007a382bec787fdfc36e4cf Mon Sep 17 00:00:00 2001 From: Michael Klishin Date: Sat, 3 May 2025 11:41:49 -0400 Subject: [PATCH] 4.1.0 release notes edits --- release-notes/4.1.0.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/release-notes/4.1.0.md b/release-notes/4.1.0.md index d3961e331c..47b1e0e16b 100644 --- a/release-notes/4.1.0.md +++ b/release-notes/4.1.0.md @@ -59,10 +59,16 @@ Clients that do override `frame_max` now must use values of 8192 bytes or greate We recommend using the default server value of `131072`: do not override the `frame_max` key in `rabbitmq.conf` and do not set it in the application code. +### Node.js `amqplib` Must Be Upgraded + [`amqplib`](https://github.com/amqp-node/amqplib/) is a popular client library that has been using a low `frame_max` default of `4096`. Its users must [upgrade to a compatible version](https://github.com/amqp-node/amqplib/blob/main/CHANGELOG.md#v0107) (starting with `0.10.7`) or explicitly use a higher `frame_max`. +`amqplib` versions older than `0.10.7` will not be able to connect to +RabbitMQ 4.1.0 and later versions due to the initial AMQP 0-9-1 maximum frame size +increase covered above. + ### MQTT