amqp-client fails to connect to a 4.1.0 node without setting a frame_max higher than its default

[YvesZelros]

Describe the bug

I am facing to this error with the JS client amqp-connection-manager version 4.1.14

error: FORMATTER CRASH: {"closing AMQP connection ~tp (~ts):~nfailed to negotiate connection parameters: ~ts",[<0.7441.0>,<<"10.11.11.54:58878 -> 10.11.1.173:5672">>,"3s","negotiated frame_max = 4096 is lower than the minimum allowed value (8192)"]}

I try to set the rabbitmq config initial_frame_max = 4096 but that not help ...

Finally only why to fix it was to add frameMax on the connection url ... amqp://localhost?frameMax=0x2000

Seem to be relative to this change =>
#13541

Reproduction steps

1. Use the JS client amqp-connection-manager version 4.1.14
2. And open a connection

Expected behavior

Connection should be success without adding frameMax on the url parameter.

Additional context

No response

[michaelklishin]

@YvesZelros your client most likely uses a frame_max of 4096 by default. It should not, or it should use the server's default of 131072.

[michaelklishin]

#13541 hasn't shipped in any release. In any case, using the standard (server, most client libraries) default would avoid this issue for any version. There is no reason to use such a small frame_max limit. It does not make the actual frames smaller.

[YvesZelros]

@michaelklishin Can be, I juste inform you that the frame_max introduce a change breaking change on the library amqp that is the most used in JS.

As minimum it should document it on the next release note ...

https://github.com/search?q=repo%3Aamqp-node%2Famqplib%20frameMax&type=code

[michaelklishin]

@YvesZelros it is documented in 4.1.0 release notes

[michaelklishin]

amqp-node/amqplib#787