activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Bertram (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-686) forceFailover/server.stop() does not shut down JVM
Date Fri, 19 Aug 2016 17:59:20 GMT

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

Justin Bertram commented on ARTEMIS-686:
----------------------------------------

I think what may be happening is that the "web" component (i.e. the Jetty server) is not being
stopped when the client stops the broker because the broker doesn't know about the web component.
 The web component is started by org.apache.activemq.artemis.cli.commands.Run.

> 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, run_artemis.sh
>
>
> 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