[jboss-jira] [JBoss JIRA] (WFCORE-998) Error executing composite op in domain with two hosts

[Brian Stansberry (JIRA)]

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

Brian Stansberry commented on WFCORE-998:
-----------------------------------------

Ah, I didn't notice yesterday that the target address of the main request was [], not host=macbook/server=server-four. There is probably a bug in how the HC deals with a composite op for [] with steps that target specific remote processes such that it assumes it can proxy the request. What it does is build up this:

{code}
{
    "operation" => "composite",
    "address" => [
            ("host" => "macbook-pro.fritz.box"),
            ("server" => "server-four")
        ],
    "steps" => [{
        "address" => []],
        "operation" => "read-resource-description",
        "operations" => true,
        "access-control" => "combined-descriptions",
        "include-aliases" => true
    }]
}
{code}

and attempts to execute that step, assuming it will be proxied to the remote process. But for a stopped server, there is no ability to proxy the request to a remote server, and the local resource that exists on the HC for that stopped server tries to handle it and can't.

The fix for this would be to have the HC realize the server is not running and not use the handling that it normally uses for connected servers. (I'm thinking the fix is likely in HostControllerExecutionSupport).

If this is fixed, you're not going to get the same r-r-d for /host=macbook/server=server-four when it's not running as you do when it is running. A non-running server resource just exposes on or two status attributes and ops to start the server.

A workaround for this is to not wrap the request in a composite.

> Error executing composite op in domain with two hosts
> -----------------------------------------------------
>
>                 Key: WFCORE-998
>                 URL: https://issues.jboss.org/browse/WFCORE-998
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Domain Management
>            Reporter: Heiko Braun
>            Assignee: Brian Stansberry
>             Fix For: 2.0.0.CR6
>
>
> {noformat}
>  Tue Sep 22 16:35:42 GMT+200 2015
> Failed to create security context for host=macbook-pro.fritz.box/server=server-four
> Unexpected HTTP response: 500
> Request
> {
>     "operation" => "composite",
>     "address" => [],
>     "steps" => [{
>         "address" => [
>             ("host" => "macbook-pro.fritz.box"),
>             ("server" => "server-four")
>         ],
>         "operation" => "read-resource-description",
>         "operations" => true,
>         "access-control" => "combined-descriptions",
>         "include-aliases" => true
>     }]
> }
> Response
> Internal Server Error
> {
>     "outcome" => "failed",
>     "result" => {"step-1" => undefined},
>     "failure-description" => {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"main-server-group" => {"host" => {"macbook-pro.fritz.box" => {"server-four" => "WFLYCTL0031: No operation named 'composite' exists at address [
>     (\"host\" => \"macbook-pro.fritz.box\"),
>     (\"server\" => \"server-four\")
> ]"}}}}}},
>     "rolled-back" => true,
>     "server-groups" => {"main-server-group" => {"host" => {"macbook-pro.fritz.box" => {"server-four" => {"response" => {
>         "outcome" => "failed",
>         "failure-description" => "WFLYCTL0031: No operation named 'composite' exists at address [
>     (\"host\" => \"macbook-pro.fritz.box\"),
>     (\"server\" => \"server-four\")
> ]",
>         "rolled-back" => true
>     }}}}}}
> }
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)