[jboss-jira] [JBoss JIRA] (AS7-4491) Structure of the "server-groups" node in a multi-server operation response breaks if multiple hosts use the same server names

[Kabir Khan (JIRA)]

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

Kabir Khan commented on AS7-4491:
---------------------------------

The current output for the work I am doing on http://issues.jboss.org/browse/AS7-4468, I end up with the following output. kabirs-macbook-pro.local is the slave, and misses the response headers.

{code}
[domain at localhost:9999 /] /socket-binding-group=full-sockets:remove
{
    "outcome" => "success",
    "result" => undefined,
    "server-groups" => {"main-server-group" => {"host" => {
        "kabirs-macbook-pro.local" => {
            "server-one" => {"response" => {
                "outcome" => "success",
                "result" => undefined
            }},
            "server-two" => {"response" => {
                "outcome" => "success",
                "result" => undefined
            }}
        },
        "master" => {
            "server-one" => {"response" => {
                "outcome" => "success",
                "response-headers" => {
                    "operation-requires-restart" => true,
                    "process-state" => "restart-required"
                }
            }},
            "server-two" => {"response" => {
                "outcome" => "success",
                "response-headers" => {
                    "operation-requires-restart" => true,
                    "process-state" => "restart-required"
                }
            }}
        }
    }}}
}
{code}

The slave-> server-one/-two communication is handled via ProxyStepHandler, which gets the correct results from the server:
{code}
{
    "outcome" => "success",
    "response-headers" => {
        "operation-requires-restart" => true,
        "process-state" => "restart-required"
    }
}
{code}
However it has no way of propagating that back in the OperationContext, only the result. So once the the slave ModelController is done with the operation, the results sent back to the master are:
{code}
{
    "outcome" => "success",
    "result" => undefined
}
{code}



                
> Structure of the "server-groups" node in a multi-server operation response breaks if multiple hosts use the same server names
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AS7-4491
>                 URL: https://issues.jboss.org/browse/AS7-4491
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Domain Management
>    Affects Versions: 7.1.1.Final
>            Reporter: Brian Stansberry
>            Assignee: Kabir Khan
>            Priority: Critical
>             Fix For: 7.1.2.Final-redhat1
>
>
> See "Multi-Server Responses" on https://docs.jboss.org/author/display/AS71/Management+API+reference#ManagementAPIreference-responseformat:
> "server-groups" => {
>         "groupA" => {
>             "serverA-1" => {
>                 "host" => "host1",
>                 "response" => {
>                     "outcome" => "success",
>                     "result" => undefined
>                 }
>             },
>             "serverA-2" => {
>                 "host" => "host2",
>                 "response" => {
>                     "outcome" => "success",
>                     "result" => undefined
>                 }
>             }
>         },
>         ....
> What if on both hosts the server was named "serverA" ? The result for one would replace the result for the other.
> It's important to allow hosts to re-use server names, as this makes it practical to re-use a host.xml across multiple installations; e.g. in single AMI used on many EC2 instances.

--
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