[
https://issues.apache.org/jira/browse/ARTEMIS-2620?focusedWorklogId=386023&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-386023
]
ASF GitHub Bot logged work on ARTEMIS-2620:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 12/Feb/20 16:08
Start Date: 12/Feb/20 16:08
Worklog Time Spent: 10m
Work Description: gaohoward commented on pull request #2982: ARTEMIS-2620
Avoid Exception on client when large message file corrupted
URL: https://github.com/apache/activemq-artemis/pull/2982
The broker should be more resilient so that it can avoid throwing an
exception on the client side when it encounters an invalid or empty
large message file(corrupted for any reason). It would be better to
deal with it within the broker and not allow the issue to manifest
itself on the consuming client.
Also fixed an ActiveMQServerMessagePlugin issue where beforeSend(),
afterSend(), sendOnException() are not get called with large
messages.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 386023)
Remaining Estimate: 0h
Time Spent: 10m
> Avoid Exception on client when large message file corrupted
> -----------------------------------------------------------
>
> Key: ARTEMIS-2620
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2620
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.11.0
> Reporter: Howard Gao
> Assignee: Howard Gao
> Priority: Major
> Fix For: 2.12.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The broker should be more resilient so that it can avoid throwing an
> exception on the client side when it encounters an invalid or empty large
> message file(corrupted for any reason). It would be better to deal with it
> within the broker and not allow the issue to manifest itself on the consuming
> client.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
