[
https://issues.apache.org/jira/browse/ARTEMIS-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erwin Dondorp updated ARTEMIS-3353:
-----------------------------------
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.
was:
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 {{-1}} leaves the original indicator alone.
> add acceptor parameter coreMinLargeMessageSize for CORE protocol
> ----------------------------------------------------------------
>
> Key: ARTEMIS-3353
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3353
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 2.17.0
> Reporter: Erwin Dondorp
> Priority: Major
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
