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 2018/12/20 16:49:00 UTC

[jira] [Commented] (ARTEMIS-2186) Large message incomplete when server is crashed

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

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

Github user jbertram commented on the issue:

    https://github.com/apache/activemq-artemis/pull/2444
  
    @clebertsuconic, @michaelandrepearce, do you guys think this is ready to be merged now? It looks good to me since there is a test and the file is always synced on `releaseResources`.


> Large message incomplete when server is crashed
> -----------------------------------------------
>
>                 Key: ARTEMIS-2186
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2186
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>            Reporter: yangwei
>            Priority: Major
>
> When sending large message, the large message file on server side is not synced whereas the journal record or paged message is synced.
> When server crashes, large message file maybe incomplete.
> In our case, we saw an empty file when server crashed and started. Then a large message with zero size body was delivered to client, client occured exception: 
> AMQ212058: Unable to get a message.: java.lang.IndexOutOfBoundsException: readerIndex(4) + length(1) exceeds writerIndex(4): UnpooledDuplicatedByteBuf(ridx: 4, widx: 4, cap: 4, unwrapped: UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 4, widx: 4, cap: 4))@ClientLargeMessageImpl



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)