activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "clebert suconic (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-686) forceFailover/server.stop() does not shut down JVM
Date Thu, 18 Aug 2016 14:04:21 GMT

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

clebert suconic commented on ARTEMIS-686:
-----------------------------------------

What we said was.  We shouldn't hold the JVM. If you start an embedded server and something
else is holding the JVM then it will stay up. 


We need to understand if there is a non daemon thread up which would cause this. 

> forceFailover/server.stop() does not shut down JVM
> --------------------------------------------------
>
>                 Key: ARTEMIS-686
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-686
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 1.5.0
>            Reporter: Ulf Lilleengen
>         Attachments: artemis_shutdown.log, broker.xml
>
>
> After some discussion on github (https://github.com/apache/activemq-artemis/pull/725),
it was said that server.stop() should stop the JVM(). The forceFailover management operation
does call server.stop(true), but the JVM ist still running.
> Attached is a jstack of the JVM and the configuration I am running with. I'm using 1.5.0-Snapshot
from 17/8.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message