[JBoss JIRA] (WFLY-10441) mod_cluster proxy operations are incorrectly registered at the subsystem level
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-10441?page=com.atlassian.jira.plugin... ]
Radoslav Husar updated WFLY-10441:
----------------------------------
Affects Version/s: 13.0.0.Final
> mod_cluster proxy operations are incorrectly registered at the subsystem level
> ------------------------------------------------------------------------------
>
> Key: WFLY-10441
> URL: https://issues.jboss.org/browse/WFLY-10441
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 13.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
>
> mod_cluster proxy operations are incorrectly registered at the subsystem level, {{/subsystem=modcluster}}. These operations are pertaining to a specific mod_cluster configuration, so they should have been registered at the {{/subsystem=modcluster/mod-cluster-config=CONFIGURATION}} level.
> These need to be deprecated and registered at the correct location.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (WFLY-10473) mod_cluster subsystem add operation attempts to start services prematurely
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-10473?page=com.atlassian.jira.plugin... ]
Radoslav Husar updated WFLY-10473:
----------------------------------
Affects Version/s: 13.0.0.Final
> 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
> Affects Versions: 13.0.0.Beta1, 13.0.0.Final
> 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@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 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.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (WFLY-10467) Drop support for mod_cluster subsystem model versions prior 1.5.0
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-10467?page=com.atlassian.jira.plugin... ]
Radoslav Husar updated WFLY-10467:
----------------------------------
Affects Version/s: 13.0.0.Final
> Drop support for mod_cluster subsystem model versions prior 1.5.0
> -----------------------------------------------------------------
>
> Key: WFLY-10467
> URL: https://issues.jboss.org/browse/WFLY-10467
> Project: WildFly
> Issue Type: Task
> Components: mod_cluster
> Affects Versions: 13.0.0.Beta1, 13.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Minor
>
> * No need to keep unused model version 1.4.0 in enumeration.
> * No need to keep transformer logic prior 1.5.0 which is the lowest supported (session draining strategy was supported in EAP 6.3/6.4 so no need to transform to older).
> * No need for org.wildfly.extension.mod_cluster.controller.SessionDrainingStrategyChecker
> * No need for 1.5.0 config in org.wildfly.extension.mod_cluster.ModClusterTransformersTestCase#createFailedOperationConfig
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months