[ 
https://issues.apache.org/jira/browse/ARTEMIS-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064051#comment-16064051
 ] 

ASF GitHub Bot commented on ARTEMIS-1220:
-----------------------------------------

Github user gaohoward commented on the issue:

    https://github.com/apache/activemq-artemis/pull/1351
  
    good point. Thanks!
    
    On Tue, Jun 27, 2017 at 2:33 AM, asfgit <[email protected]> wrote:
    
    > Closed #1351 <https://github.com/apache/activemq-artemis/pull/1351> via
    > 1888e2c
    > 
<https://github.com/apache/activemq-artemis/commit/1888e2ca4f30be5f02c886b36a3c431c04c261a9>
    > .
    >
    > —
    > You are receiving this because you were mentioned.
    > Reply to this email directly, view it on GitHub
    > <https://github.com/apache/activemq-artemis/pull/1351#event-1139201726>,
    > or mute the thread
    > 
<https://github.com/notifications/unsubscribe-auth/AAp476FuUIdRe4S4qDi7TQr950ipbdVbks5sH_l-gaJpZM4N_Z9d>
    > .
    >



> Diverted LargeMessage file corrupted during replication
> -------------------------------------------------------
>
>                 Key: ARTEMIS-1220
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1220
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 1.5.5, 2.1.0
>            Reporter: Howard Gao
>            Assignee: Howard Gao
>             Fix For: 1.5.6, 2.2.0
>
>
> When a large message is being diverted, a new copy of the original message is 
> created and replicated (if there is a backup) to the backup. 
> In LargeServerMessageImpl.copy(long) it reuse a byte array to copy message 
> body. It is possible that one block of date is read into the byte array 
> before the previous read has been replicated, causing the replicated bytes to 
> corrupt.
> If we make a copy of the byte array before replication, the corruption of 
> data will be avoided.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to