frame_too_large issue

[bsanthanam-equinix]

Describe the bug

We are getting below error in Boomi EAI side while connecting to the RabbitMQ 4.X version.

[ERROR] connection error; protocol method: #method<connection.close>(reply-code=501, reply-text=FRAME_ERROR - type 2, all octets = <<>>: {frame_too_large,34383,16376}, class-id=0, method-id=0)

Kindly help us on how to resolve this error

Reproduction steps

...

Expected behavior

It should able to connect and send data

Additional context

No response

[michaelklishin]

@bsanthanam-equinix we cannot suggest anything with this much information. Take a traffic capture and see what's going on.

Collect server logs and share more than one line.

We do not guess in this community.

[michaelklishin]

One of the common issues that can cause incorrect binary data to be sent on the wire is concurrent publishing on a shared channel. With all but one (.NET) clients this is explicitly not allowed or supported. Use one channel per thread and/or synchronize such publishing.

Explained about a million times before, here we go again. A published message of non-zero length results in three or more frames on the wire:

[basic.publish]{1} [content header]{1} [message body]+

With two concurrent publishers on a shared channel this can become

[basic.publish 1] [basic.publish 2] [content header 1] [message body 1] [message body 2] [content header 2] [message body 2]

or a comparable sequence of randomly interleaved frames, which would not be a valid frame sequence on a single channel.

Without relevant publisher code, full RabbitMQ node logs and a traffic capture there's nothing for us to work with => that's the end of this discussion