[jboss-jira] [JBoss JIRA] (AS7-4413) Addressing the shutdown command to an unknown host results in shutdown of the Domain Controller

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/AS7-4413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated AS7-4413:
----------------------------------

        Summary: Addressing the shutdown command to an unknown host results in shutdown of the Domain Controller  (was: shutting down slave host with jboss-cli.sh stops Domain Controller when slave is started with --cached-dc)
    Description: 
This command from the CLI results in shutdown of the DC (note there is no registered host named "bogus"):

$ ./jboss-cli.sh -c
[domain at localhost:9999 /] /host=bogus:shutdown
{"outcome" => "success"}


To maintain history, following is the original JIRA description, but the --cached-dc stuff below is not really relevant. Starting the slave with --cached-dc just meant it didn't register with the DC the CLI is connecting to at $DOMAIN_CONTROLLER_HOST:$DOMAIN_CONTROLLER_PORT, so the effect is the same as my host=bogus example above. 


NOTE: this is related to AS7-4281 (see https://issues.jboss.org/browse/AS7-4281?focusedCommentId=12682058&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12682058 )

when a slave host is started with -cached-dc option, executing "jboss-cli.sh -c command=/host=$SLAVE_HOSTNAME:shutdown --controller=$DOMAIN_CONTROLLER_HOST:$DOMAIN_CONTROLLER_PORT --user=$HOSTNAME --password=$PASSWORD" will stop the Domain Controller instead stopping slave host. If I execute the same command without using --cached-dc option when starting slave host, it will shutdown the slave host as I expected. I am not really sure about what should do this command (stopping DC or slave -I think it should stop slave host) but it's kind of weird the behaviour depending on the --cached-dc option.

  was:
NOTE: this is related to AS7-4281 (see https://issues.jboss.org/browse/AS7-4281?focusedCommentId=12682058&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12682058 )

when a slave host is started with -cached-dc option, executing "jboss-cli.sh -c command=/host=$SLAVE_HOSTNAME:shutdown --controller=$DOMAIN_CONTROLLER_HOST:$DOMAIN_CONTROLLER_PORT --user=$HOSTNAME --password=$PASSWORD" will stop the Domain Controller instead stopping slave host. If I execute the same command without using --cached-dc option when starting slave host, it will shutdown the slave host as I expected. I am not really sure about what should do this command (stopping DC or slave -I think it should stop slave host) but it's kind of weird the behaviour depending on the --cached-dc option.

       Priority: Blocker  (was: Critical)


Updated the summary and description to better highlight the full scope of the issue.
                
> Addressing the shutdown command to an unknown host results in shutdown of the Domain Controller
> -----------------------------------------------------------------------------------------------
>
>                 Key: AS7-4413
>                 URL: https://issues.jboss.org/browse/AS7-4413
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Domain Management
>    Affects Versions: 7.1.1.Final
>            Reporter: Manel Martinez
>            Assignee: Brian Stansberry
>            Priority: Blocker
>             Fix For: 7.1.2.Final-redhat1
>
>
> This command from the CLI results in shutdown of the DC (note there is no registered host named "bogus"):
> $ ./jboss-cli.sh -c
> [domain at localhost:9999 /] /host=bogus:shutdown
> {"outcome" => "success"}
> To maintain history, following is the original JIRA description, but the --cached-dc stuff below is not really relevant. Starting the slave with --cached-dc just meant it didn't register with the DC the CLI is connecting to at $DOMAIN_CONTROLLER_HOST:$DOMAIN_CONTROLLER_PORT, so the effect is the same as my host=bogus example above. 
> NOTE: this is related to AS7-4281 (see https://issues.jboss.org/browse/AS7-4281?focusedCommentId=12682058&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12682058 )
> when a slave host is started with -cached-dc option, executing "jboss-cli.sh -c command=/host=$SLAVE_HOSTNAME:shutdown --controller=$DOMAIN_CONTROLLER_HOST:$DOMAIN_CONTROLLER_PORT --user=$HOSTNAME --password=$PASSWORD" will stop the Domain Controller instead stopping slave host. If I execute the same command without using --cached-dc option when starting slave host, it will shutdown the slave host as I expected. I am not really sure about what should do this command (stopping DC or slave -I think it should stop slave host) but it's kind of weird the behaviour depending on the --cached-dc option.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira