Github user rvsoni commented on the issue:
https://github.com/apache/activemq-artemis/pull/871
We ware having some issue in NFS server used as shared store for journals
and largemessage store, so write to large file got interrupted due to client
close connection.
class NIOSequentialFile is haveing fix related to handling
ClosedChannelException, it was only missed in two method (copy,remane) of
AbstractSequentialFile which caused server shutdown.
We got this issue in HornetQ, and Artemis also has same code base.
This is related to https://bugzilla.redhat.com/show_bug.cgi?id=1296634
```
16:40:38,947 WARN [org.hornetq.core.server] (Old I/O server worker
(parentId: 1527657329, [id: 0x5b0e3371, /10.100.40.199:5445]), runningThrea
d=Thread-7391
(HornetQ-remoting-threads-HornetQServerImpl::serverUUID=5a56fa30-e71f-11e5-8294-e926e7e7d82c-1188589496-865516095))
HQ222010: Cri
tical IO Error, shutting down the server. file=NIOSequentialFile
/opt/idsk/shared/messaging/live/largemessages/8653688763.msg, message=null: Ho
rnetQException[errorType=IO_ERROR message=null]
at
org.hornetq.core.journal.impl.NIOSequentialFile.internalWrite(NIOSequentialFile.java:359)
[hornetq-journal-2.3.25.SP8-redhat-1.jar:2
.3.25.SP8-redhat-1]
at
org.hornetq.core.journal.impl.NIOSequentialFile.writeDirect(NIOSequentialFile.java:312)
[hornetq-journal-2.3.25.SP8-redhat-1.jar:2.3
.25.SP8-redhat-1]
at
org.hornetq.core.journal.impl.AbstractSequentialFile.copyTo(AbstractSequentialFile.java:130)
[hornetq-journal-2.3.25.SP8-redhat-1.ja
r:2.3.25.SP8-redhat-1]
at
org.hornetq.core.persistence.impl.journal.LargeServerMessageImpl.finishCopy(LargeServerMessageImpl.java:326)
[hornetq-server-2.3.25.
SP8-redhat-1.jar:2.3.25.SP8-redhat-1]
at org.hornetq.core.server.impl.DivertImpl.route(DivertImpl.java:94)
[hornetq-server-2.3.25.SP8-redhat-1.jar:2.3.25.SP8-redhat-1]
at
org.hornetq.core.postoffice.impl.DivertBinding.route(DivertBinding.java:108)
[hornetq-server-2.3.25.SP8-redhat-1.jar:2.3.25.SP8-redh
at-1]
```
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
