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 subversion and git services (JIRA)" <ji...@apache.org> on 2019/01/19 08:17: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=16746983#comment-16746983 ]
ASF subversion and git services commented on ARTEMIS-2186:
----------------------------------------------------------
Commit 3954f0183f63291722f504e7d41beb052a6639aa in activemq-artemis's branch refs/heads/master from yang wei
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=3954f01 ]
ARTEMIS-2186 Large message incomplete when server is crashed
> 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
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)