[
https://issues.apache.org/jira/browse/AMQ-7128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16740444#comment-16740444
]
Jeff Genender commented on AMQ-7128:
------------------------------------
Hi Martin, good to see you! Yes, the shutdown issue could happen on a stale
file lock. I would look at your OS and logs for the OS, as this will likely be
the culprit. The stale lock is going to be caused by the OS (NFS/SMB/etc) and
that may end up requiring some tuning and investigation to see why there is an
issue. I do not think this has to do with ActiveMQ.
> Broker does not react on IOException: Stale file handle and does not fully
> shutdown
> -----------------------------------------------------------------------------------
>
> Key: AMQ-7128
> URL: https://issues.apache.org/jira/browse/AMQ-7128
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.15.4
> Reporter: Martin Lichtin
> Priority: Major
> Attachments: activemq-stale-file-handle-andshutdown-issue.txt
>
>
> Seeing a situation during which the broker can no longer write to the KahaDB
> filesystem (IOException: Stale file handle). This "seems" to initiate a
> shutdown (as indicated by subsequent 'Async Writer Thread Shutdown'
> exceptions), but nothing happens.
> Only after around 3 hours, something does happen that triggers the actual
> stopping of the broker service.
> However, then the shutdown never completes as the IOExceptionHandler that
> initiates the broker.stop() is called again, and the throws a
> 'SuppressReplyException' which KahaDB (wrongly?) interprets as yet another
> issue and itself fails to stop the persistence adapter.
> Attaching a log where all this can be observed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
