[
https://issues.apache.org/jira/browse/AMQ-8412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17487298#comment-17487298
]
Christopher L. Shannon commented on AMQ-8412:
---------------------------------------------
Given that the reported size in the client will generally be larger than the
broker detected frame size due to how the encoding works (especially with
compression enabled) I am going to most likely be a -1 on this change unless
it's disabled by default as it would definitely break existing users sending
messages that are close to the configured encoded size (they will suddenly fail
when they used to work).
The only way for this to truly work correctly on the client size would be to
marshal the message first using openwire so all the settings are applied like
compression and then check the actual frame on the client side before it's sent
over the wire so that the what is checked is the same thing the broker gets.
> Return a well-formed response to clients when max message size is sent
> ----------------------------------------------------------------------
>
> Key: AMQ-8412
> URL: https://issues.apache.org/jira/browse/AMQ-8412
> Project: ActiveMQ
> Issue Type: New Feature
> Components: JMS client
> Reporter: Matt Pavlovich
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 5.17.0, 5.16.4
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Currently, clients get an inconclusive exception when a message that is too
> large is sent. We should send a well-formed message, and then close.
> Options:
> 1. Change the current IOException to something else to fall within existing
> exception flow
> 2. Update current exception handling to send ExceptionResponse w/ the max
> message size message to the client before closing
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
