You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/01/24 16:27:00 UTC
[jira] [Work logged] (AMQ-8412) Return a well-formed response to clients when max message size is sent
[ https://issues.apache.org/jira/browse/AMQ-8412?focusedWorklogId=713882&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-713882 ]
ASF GitHub Bot logged work on AMQ-8412:
---------------------------------------
Author: ASF GitHub Bot
Created on: 24/Jan/22 16:26
Start Date: 24/Jan/22 16:26
Worklog Time Spent: 10m
Work Description: mattrpav opened a new pull request #747:
URL: https://github.com/apache/activemq/pull/747
…e size exceeded
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: gitbox-unsubscribe@activemq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 713882)
Remaining Estimate: 0h
Time Spent: 10m
> 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: Task
> Reporter: Matt Pavlovich
> Assignee: Matt Pavlovich
> Priority: Major
> Fix For: 5.17.0, 5.16.4
>
> Time Spent: 10m
> 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)