Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Thu, 5 Nov 2015 02:31:27 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: issues@activemq.apache.org
Message-ID: <JIRA.12910365.1446649702000.159003.1446690687698@Atlassian.JIRA>
In-Reply-To: <JIRA.12910365.1446649702000@Atlassian.JIRA>
References: <JIRA.12910365.1446649702000@Atlassian.JIRA>
 <JIRA.12910365.1446649702655@arcas>
Subject: [jira] [Commented] (ARTEMIS-297) Handle exceptions during server
 stop
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ARTEMIS-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14990987#comment-14990987 ] 

ASF GitHub Bot commented on ARTEMIS-297:
----------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/activemq-artemis/pull/234


> 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)