You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PR #1220's intent is to prevent large allocations due to bad incoming data, or large messages. The fix checks that the individual frame's size does not exceed the maximum message size, but it does not take into account the case where a large message is split into multiple frames. When combined, the message body may exceed the max message size.
Fixes#1356
* Fix `TestProperties` test so that expected / actual are correct args.
* Fix passing MaxInboundMessageBodySize via connection config
* Make default RMQ max message size constant Internal
* Ensure that maximum max message size is not overriden
Fixes#1356
* Fix `TestProperties` test so that expected / actual are correct args.
* Fix passing MaxInboundMessageBodySize via connection config
* Make default RMQ max message size constant Internal
* Ensure that maximum max message size is not overriden
Describe the bug
PR #1220's intent is to prevent large allocations due to bad incoming data, or large messages. The fix checks that the individual frame's size does not exceed the maximum message size, but it does not take into account the case where a large message is split into multiple frames. When combined, the message body may exceed the max message size.
Related to rabbitmq/rabbitmq-java-client#1062
Reproduction steps
N/A
Expected behavior
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: