-
Bug
-
Resolution: Done
-
Major
-
13.0.0.Beta1, 13.0.0.Final
-
None
This has been a problem multiple times in the past. Even a single subsystem add operation like
[standalone@localhost:9990 /] /subsystem=modcluster:add
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
causes failures
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"
This is fixed 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.
- is incorporated by
-
WFLY-10439 Modernize mod_cluster subsystem
-
- Closed
-