[ARTEMIS-3353] add acceptor parameter coreMinLargeMessageSize for CORE protocol

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.17.0
• Component/s: Broker
• Assignee: Unassigned
• Reporter: Erwin Dondorp
• Created: 16/Jun/21 21:01
• Updated: 20/Jun/21 17:18
• Resolved: 20/Jun/21 17:18

Description

The handling of large messages differs significantly between messaging protocols.
See also https://activemq.apache.org/components/artemis/documentation/latest/large-messages.html

For CORE, currently, the producer decides on the fact whether a message is large. It does that by using minLargeMessageSize=12345 (default=100K) in the connection-url. The client uses this value to determine whether it is large size.
For AMQP, currently, the broker decides on that fact. It does that by using amqpMinLargeMessageSize=12345 in the acceptor-url.
This means that the responsibility is not always in the same place. And the responsibility is therefore not with the same teams, as we have a team that maintains the broker and teams that maintain consumer/producer applications. And there is also some freedom in using amqp and/or core.

My goal is to make the client connections as simple as possible.

My proposal is to add parameter coreMinLargeMessageSize to the acceptor urls for use by the CORE protocol. When the value is set, it indicates that the large message flag must be reset by the broker based on that parameter-value. Not setting the value or using "" leaves the original indicator alone.