You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Emmanuel Hugonnet (Jira)" <ji...@apache.org> on 2022/01/31 12:38:00 UTC
[jira] [Commented] (ARTEMIS-3085) Support registering IOCriticalErrorListener on the broker
[ https://issues.apache.org/jira/browse/ARTEMIS-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17484644#comment-17484644 ]
Emmanuel Hugonnet commented on ARTEMIS-3085:
--------------------------------------------
Sorry guys I missed the notifications.
The idea was to be able to do somehing when such an error occurs. Currently if there is a network failure for a nfs mount point or a JBDC journal, the broker shutdowns. The idea was to be able to detect such a case and try to restart the broker once that network issue has been resolved.
> Support registering IOCriticalErrorListener on the broker
> ---------------------------------------------------------
>
> Key: ARTEMIS-3085
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3085
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 2.16.0
> Reporter: Emmanuel Hugonnet
> Priority: Major
> Labels: easy
>
> There is no way to register a IOCriticalErrorListener on the broker to customize the behaviour on critical IO errors
--
This message was sent by Atlassian Jira
(v8.20.1#820001)