[
https://issues.apache.org/jira/browse/AMQ-8412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17487213#comment-17487213
]
Matt Pavlovich edited comment on AMQ-8412 at 2/4/22, 6:06 PM:
--------------------------------------------------------------
[~cshannon] Before this change, the broker closes the connection on max message
failure without delivering any packets to the client. The is represented on the
client-side as an IOException and no indication of why. When failover is
configured, it would infinitely retry a message that is too large.
With this change, a well formed exception is returned to the client. The client
does not *need* to close the connection, they can if they choose-- or the "too
large" message could be logged and the next one goes through on the same
connection without a problem.
was (Author: mattrpav):
[~cshannon]the broker closes the connection on max message failure. The client
gets an IOException and no indication of why. When failover is configured, it
would infinitely retry a message that is too large.
With this change, a well formed exception is returned to the client. The client
does not *need* to close the connection, they can if they choose-- or the "too
large" message could be logged and the next one goes through on the same
connection without a problem.
> 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)
