[jboss-jira] [JBoss JIRA] (AS7-6387) Improper error handling when attempting to remove a server-config with a running server

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/AS7-6387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12751168#comment-12751168 ] 

Brian Stansberry commented on AS7-6387:
---------------------------------------

Note that something has definitely changed in the error reporting in master vs 7.1. Even when following Osamu Nogano's steps in master, I don't get the error message he reports. It fails on ServerRemoveHandler L70, but OFE message doesn't propagate out.
                
> Improper error handling when attempting to remove a server-config with a running server
> ---------------------------------------------------------------------------------------
>
>                 Key: AS7-6387
>                 URL: https://issues.jboss.org/browse/AS7-6387
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Domain Management
>    Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
>            Reporter: Brian Stansberry
>            Assignee: Emanuel Muckenhuber
>             Fix For: 7.2.0.Alpha1
>
>
> Trying to remove the config for server-one while it's still running produces an uninformative failure:
> [domain at localhost:9999 /] /host=master/server-config=server-one:remove
> {
>     "outcome" => "failed",
>     "result" => undefined,
>     "rolled-back" => true,
>     "server-groups" => undefined
> }
> An EAP 6 user reported a similar problem but with a different response:
> [domain at localhost:9999 /] /host=xyz/server-config=as1:remove
> {
>     "outcome" => "success",
>     "result" => {
>         "outcome" => "failed",
>         "failure-description" => "[core-service, path, server-config, system-property, jvm, interface]",
>         "rolled-back" => true
>     },
>     "failure-description" => undefined
> }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira