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
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-itemsmax_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.
The text was updated successfully, but these errors were encountered:
Hi @tboon-cfgms thanks for reporting this!
I think we can have both quite easily but let's start with just maxInboundMessageSize first I would say
A PR is welcome for sure
UPDATE: I've just opened a PR to address this #991
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 exposessetMaxInboundMessageSize
as a method onConnectionFactory
-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
.The text was updated successfully, but these errors were encountered: