[
https://issues.apache.org/jira/browse/ARTEMIS-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16700302#comment-16700302
]
ASF GitHub Bot commented on ARTEMIS-2186:
-----------------------------------------
Github user sebthom commented on the issue:
https://github.com/apache/activemq-artemis/pull/2444
From the description it is unclear what is meant by "server crash". JVM
crash or host/machine crash. If the problem occured with unexpected JVM process
termination maybe the broker can be started in a separate JVM processes and
SIGKILLed while doing large message processing to reproduce the issue.
> 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)
