Is there a reason why in connection.js the maxFrameBuffer is set to the value configured within the (RabbitMQ) server, while the AMQPParser has a fixed maxFrameBuffer?
I have the problem, that a producer of mine is able to send larger frames but a consumer cannot receive it because of an Oversized Frame error.
tobias-neubert
commented
9 years ago
Is there a reason why in connection.js the maxFrameBuffer is set to the value configured within the (RabbitMQ) server, while the AMQPParser has a fixed maxFrameBuffer?
I have the problem, that a producer of mine is able to send larger frames but a consumer cannot receive it because of an Oversized Frame error.