[
https://issues.apache.org/jira/browse/ARTEMIS-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14990986#comment-14990986
]
ASF subversion and git services commented on ARTEMIS-297:
---------------------------------------------------------
Commit 046c3b19422c821136c36bf65f65e674e071a44f in activemq-artemis's branch
refs/heads/master from [~martyntaylor]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=046c3b1 ]
ARTEMIS-297 Handle Exceptions during server stop
Stopping the server should be able to handle exceptions thrown by
individual components. Before this patch the stop method would throw
any raised exception and exit. This can lead to partial shutdowns of
the server resulting in leaking threads. This patch catches any
component exceptions and logs an appropriate error message, allowing the
server to properly shutdown.
> Handle exceptions during server stop
> ------------------------------------
>
> Key: ARTEMIS-297
> URL: https://issues.apache.org/jira/browse/ARTEMIS-297
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Martyn Taylor
>
> The server stop method is quite brittle. If any component throws an
> exception during shutdown, the exception is thrown and the method exits.
> Instead the stop method on the server should be able to handle such
> exceptions and continue shutting down all components and eventually stop the
> ExecutorServices. Failure to do so can lead to leaking threads.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
