[
https://issues.apache.org/jira/browse/ARTEMIS-2620?focusedWorklogId=435242&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-435242
]
ASF GitHub Bot logged work on ARTEMIS-2620:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 19/May/20 22:45
Start Date: 19/May/20 22:45
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on pull request #2982:
URL: https://github.com/apache/activemq-artemis/pull/2982#issuecomment-631126325
I agree with adding a plugin event..
but I don't think we should change semantics on the sending exceptions to
the client.
----------------------------------------------------------------
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: 435242)
Time Spent: 40m (was: 0.5h)
> 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.14.0
>
> Time Spent: 40m
> 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)
