[jboss-jira] [JBoss JIRA] (WFCORE-932) stop-embedded-server stops the embedded host controller and vice versa
Petr Kremensky (JIRA)
issues at jboss.org
Fri Aug 28 08:33:05 EDT 2015
[ https://issues.jboss.org/browse/WFCORE-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Petr Kremensky moved JBEAP-930 to WFCORE-932:
---------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-932 (was: JBEAP-930)
Workflow: GIT Pull Request workflow (was: CDW v1)
Component/s: CLI
Domain Management
(was: CLI)
(was: Domain Management)
Target Release: (was: 7.0.0.GA)
Affects Version/s: 2.0.0.Beta4
(was: 7.0.0.DR9)
> stop-embedded-server stops the embedded host controller and vice versa
> ----------------------------------------------------------------------
>
> Key: WFCORE-932
> URL: https://issues.jboss.org/browse/WFCORE-932
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Domain Management
> Affects Versions: 2.0.0.Beta4
> Reporter: Petr Kremensky
> Assignee: Ken Wills
> Priority: Minor
>
> We have four new commands for controlling the lifecycle of embedded instances:
> * *embed-server* - launch embedded standalone
> * *stop-embedded-server* - stop embedded standalone
> * *embed-host-controller* - launch embedded host
> * *stop-embedded-host-controller* - stop embedded host
> \\
> I am able stop embedded standalone by *stop-embedded-host-controller* and embedded host controller by *stop-embedded-server*.
> {noformat}
> [disconnected /] embed-server
> [standalone at embedded /] stop-embedded-host-controller
> [disconnected /] embed-host-controller
> 14:22:18,781 INFO [org.jboss.modules] (AeshProcess: 15) JBoss Modules version 1.4.3.Final
> [domain at embedded /] stop-embedded-server
> [disconnected /]
> {noformat}
> \\
> A question comes to my mind, do we need two commands for stopping the embedded instance?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
More information about the jboss-jira
mailing list