[jboss-jira] [JBoss JIRA] (WFLY-10473) mod_cluster subsystem add operation attempts to start services prematurely

[Radoslav Husar (JIRA)]

Radoslav Husar created WFLY-10473:
-------------------------------------

             Summary: mod_cluster subsystem add operation attempts to start services prematurely
                 Key: WFLY-10473
                 URL: https://issues.jboss.org/browse/WFLY-10473
             Project: WildFly
          Issue Type: Bug
          Components: mod_cluster
            Reporter: Radoslav Husar
            Assignee: Radoslav Husar


This has been a problem multiple times in the past. Even a single subsystem add operation like

{noformat}
[standalone at localhost:9990 /] /subsystem=modcluster:add
{
    "outcome" => "success",
    "response-headers" => {
        "operation-requires-reload" => true,
        "process-state" => "reload-required"
    }
}
{noformat}

causes failures

{noformat}10:28:15,128 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 54) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "modcluster")]) - failure description: "WFLYCTL0155: 'connector' may not be null"
10:28:15,135 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 54) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "modcluster")]) - failure description: "WFLYCTL0155: 'connector' may not be null"
{noformat}

This is fixes also as a side effect to supporting multiple configurations.

Since boot time handling is required, most operations on the subsystem need to leave the server in the reload-required state.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)