[
https://issues.apache.org/jira/browse/ARTEMIS-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16701250#comment-16701250
]
ASF GitHub Bot commented on ARTEMIS-2186:
-----------------------------------------
Github user wy96f commented on the issue:
https://github.com/apache/activemq-artemis/pull/2444
> I am a bit confused as a file.close would issue a sync.
It won't. As man page said:
A successful close does not guarantee that the data has been successfully
saved to disk, as the kernel defers writes. It is not common for a file system
to flush the buffers when the stream is closed. If you need to be sure that
the data is physically stored use fsync(2). (It will depend on the disk
hardware at this point.)
> 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)
