[
https://issues.apache.org/jira/browse/AMQ-7128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16742264#comment-16742264
]
Jeff Genender commented on AMQ-7128:
------------------------------------
Unfortunately, Java is at the mercy of the OS reporting the lock is free. My
advice is to look at your OS and disk to see if it has settings to report a
freed lock. There really is not much we can do here. If you are using NFS
(and I am hoping NFS 4), there are a lot of tuning capabilities to be sure that
lock is freed, which is beyond the scope of how we can help.
> 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)
