[
https://issues.apache.org/jira/browse/ARTEMIS-2620?focusedWorklogId=648986&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-648986
]
ASF GitHub Bot logged work on ARTEMIS-2620:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 10/Sep/21 02:24
Start Date: 10/Sep/21 02:24
Worklog Time Spent: 10m
Work Description: gaohoward commented on pull request #2982:
URL: https://github.com/apache/activemq-artemis/pull/2982#issuecomment-916581478
@clebertsuconic @jbertram Sorry guys it's been a long time and this hasn't
been mentioned by any ever since. And the PR has very much outdated. I agree
with Justin that we close this at the moment.
--
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-unsubscr...@activemq.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 648986)
Time Spent: 1h 10m (was: 1h)
> 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.19.0
>
> Time Spent: 1h 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)
