Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Add way to setMaxInboundMessageBodySize #990

Open
tboon-cfgms opened this issue Sep 24, 2024 · 0 comments
Open

Feature Request: Add way to setMaxInboundMessageBodySize #990

tboon-cfgms opened this issue Sep 24, 2024 · 0 comments

Comments

@tboon-cfgms
Copy link

As data payloads get larger and larger, the default Java client value for maxInboundMessageSize of 64MB is too limiting for some use cases. AMQP spec defines the max message size as 512MB (see https://www.rabbitmq.com/docs/configure#config-items max_message_size). The Java client exposes setMaxInboundMessageSize as a method on ConnectionFactory - Fs2RabbitConfig should allow this value to be set and default to the Java client default of 64MB if not provided.

As an extension of this, add more optional configuration to allow any value in ConnectionFactory to be set beyond those currently supported. But that is a bigger ask.

I would be willing to make a PR for maxInboundMessageSize.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant