Add configuration for max inbound message size #212
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jendakol
approved these changes
Apr 29, 2024
okubis
force-pushed
the
max-inbound-messagy-body-size-config
branch
3 times, most recently
from
ca57631
to
16c7008
Compare
which is new max size limit on server side since 3.8.0 onward
okubis
force-pushed
the
max-inbound-messagy-body-size-config
branch
from
16c7008
to
e809899
Compare
jendakol
approved these changes
Apr 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change in the underlying RabbitMQ library has added support for MaxInboundMessageSize configuration with a default set to 64MB:
rabbitmq/rabbitmq-java-client#1063
This however broke the behaviour of this library for us, as we might encounter bigger messages in our usecase.
Hence this PR makes this value configurable even when using this wrapper