[
https://issues.apache.org/jira/browse/AMQ-8412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17484085#comment-17484085
]
ASF subversion and git services commented on AMQ-8412:
------------------------------------------------------
Commit afc50ee7275b5417d5768db84a9fe9054d526e7a in activemq's branch
refs/heads/activemq-5.16.x from Matt Pavlovich
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=afc50ee ]
[AMQ-8412] Client-side management of max frame size
- Store maxFrameSize on client-side
- Check messages on outbound send to send an actionable exception to the caller
- Add a reason code for max message size exceeded (client-side)
(cherry picked from commit 48d0fb11716d3490b1d76f7e8860b61324d4e82f)
> 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: Improvement
> 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)
