You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Christopher L. Shannon (Jira)" <ji...@apache.org> on 2022/02/04 17:06:00 UTC

[jira] [Commented] (AMQ-8412) Return a well-formed response to clients when max message size is sent

    [ https://issues.apache.org/jira/browse/AMQ-8412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17487185#comment-17487185 ] 

Christopher L. Shannon commented on AMQ-8412:
---------------------------------------------

It looks like the regression does show up on Jenkins:

[https://builds.apache.org/job/ActiveMQ/job/ActiveMQ/job/activemq-5.16.x/169/testReport/junit/org.apache.activemq.transport.nio/NIOMaxFrameSizeCleanupTest/testMaxFrameSizeCleanupAutoNio/]

The issue here is the message can be improved but the exception aborts before the connection gets closed. So if the patch is fixed to actually close the connection (and again write tests to verify) then it's ok.

> 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)