[ https://issues.apache.org/jira/browse/AMQ-8412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488080#comment-17488080 ]
ASF subversion and git services commented on AMQ-8412: ------------------------------------------------------ Commit 43aa1800fa91b2c6f3ce59cd14a70a3fa7165203 in activemq's branch refs/heads/main from Christopher L. Shannon [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=43aa180 ] Merge pull request #756 from mattrpav/AMQ-8412c [AMQ-8412] Update client-side maxFrameSize handling to be more symetrical with server-side > 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)