[
https://issues.apache.org/jira/browse/AMQ-7128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16742262#comment-16742262
]
Martin Lichtin commented on AMQ-7128:
-------------------------------------
Hi Jeff, nice to see you as well :)
You're right, when the underlying filesystem disappears, it is pretty fatal, so
not much ActiveMQ can do.
However, the current behaviour seems not ideal, it hung around in half-shutdown
mode and only at some later point in time it wanted to really shutdown. This
point was triggered when KahaDB tried to write a message (class
MessageDatabase) which in turn called the IO exception handler. Perhaps this
behaviour is all by design, I just would have expected a fail-fast reaction on
an IOException.
> 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)
