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 2020/04/17 02:33:00 UTC

[jira] [Work logged] (ARTEMIS-2620) Avoid Exception on client when large message file corrupted

     [ https://issues.apache.org/jira/browse/ARTEMIS-2620?focusedWorklogId=423879&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-423879 ]

ASF GitHub Bot logged work on ARTEMIS-2620:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 17/Apr/20 02:32
            Start Date: 17/Apr/20 02:32
    Worklog Time Spent: 10m 
      Work Description: clebertsuconic commented on issue #2982: ARTEMIS-2620 Avoid Exception on client when large message file corrupted
URL: https://github.com/apache/activemq-artemis/pull/2982#issuecomment-615004249
 
 
   rebase?
 
----------------------------------------------------------------
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:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 423879)
    Time Spent: 20m  (was: 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.13.0
>
>          Time Spent: 20m
>  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)