[
https://issues.apache.org/jira/browse/AMQ-8412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488084#comment-17488084
]
ASF subversion and git services commented on AMQ-8412:
------------------------------------------------------
Commit e630a3cc61dc62f862e2657a6652b0f2709301c9 in activemq's branch
refs/heads/activemq-5.16.x from Matt Pavlovich
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=e630a3c ]
[AMQ-8412] Update client-side maxFrameSize handling to be more symetrical with
server-side
- Handle in the OpenWireFormat class
- Add unit tests to confirm
- Verify compression is accounted for
- Verify the ability to disable using wireFormat.maxFrameSizeEnabled=false
- [cshannon] Reworked max frame size test case to add in all transports and
all client/server cases
(cherry picked from commit 67a2edbf0d7d3d43726a50743270b15b29759dec)
> 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: 4h 40m
> 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)
