[jboss-jira] [JBoss JIRA] (WFCORE-229) server-config operations "leaks" to server's resources

[Jeff Mesnil (JIRA)]

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

Jeff Mesnil updated WFCORE-229:
-------------------------------
    Summary: server-config operations "leaks" to server's resources  (was: server-config operations "leaks" to children resources)


> server-config operations "leaks" to server's resources
> ------------------------------------------------------
>
>                 Key: WFCORE-229
>                 URL: https://issues.jboss.org/browse/WFCORE-229
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Domain Management
>    Affects Versions: 1.0.0.Alpha11
>            Reporter: Jeff Mesnil
>            Assignee: Brian Stansberry
>
> Start a regular domain
> Any operations on server children with the same names that server-config operations (:start, :stop, :restart, :kill) are executed instead of being rejected because the actual resources at the operation address does not define them.
> Examples:
> {noformat}
> [domain at localhost:9990 /] /host=master/server=server-one/subsystem=undertow:start
> {
>     "outcome" => "failed",
>     "failure-description" => "WFLYCTL0158: Operation handler failed: java.util.NoSuchElementException: No child 'undertow' exists",
>     "rolled-back" => true
> }
> [domain at localhost:9990 /] /host=master/server=server-one/subsystem=undertow:stop
> {
>     "outcome" => "success",
>     "result" => "STOPPED"
> }
> [domain at localhost:9990 /] /host=master/server=server-one/subsystem=undertow:kill
> {"outcome" => "success"}
> {noformat}
> If the corresponding server-config resource is actually stopped, the operations fail because there is no resource at the operation's address.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)