-
Bug
-
Resolution: Done
-
Major
-
25.0.0.Final, 25.0.1.Final
Customer from case 02568618 identified that starting/restarting server (domain mode) in suspended mode is enabling contexts to mod_cluster.
With the change from Jira JBEAP-18610 the application contexts from running servers that are suspended are DISABLED/STOPPED from mod_cluster.
When using the following commands:
[domain@localhost:9990 /] /host=master/server=server-one:suspend() [domain@localhost:9990 /] /server-group=main-server-group:suspend-servers()
But the application contexts are started as ENABLED when starting a stopped server or restarting a running server in suspended mode. When using the following commands:
[domain@localhost:9990 /] /host=master/server-config=server-one:restart(start-mode=suspend) [domain@localhost:9990 /] /host=master/server-config=server-one:start(start-mode=suspend)
and in the standalone mode (contexts are ENABLED to mod_cluster):
sh standalone.sh -c standalone-ha.xml --start-mode=suspend
The customer request is to start the application contexts as DISABLED/STOPPED when starting a server in suspended mode.
After discussing with Chao Wang, he suggested to open this Jira for discussion. Could it be a feature request ?
- clones
-
JBEAP-19994 [GSS](7.3.z) WFLY-14121 - Starting JBoss in suspended mode and mod_cluster
- Closed
- is blocked by
-
WFCORE-5717 Upgrade Undertow to 2.2.13.Final
- Closed
-
WFLY-15675 Upgrade mod_cluster to 1.4.4.Final
- Closed
-
WFLY-15765 Upgrade WildFly Core to 18.0.0.Beta5
- Closed
- is cloned by
-
JBEAP-21289 [GSS](7.4.z) WFLY-14121 - Starting JBoss in suspended mode and mod_cluster
- Closed
- is related to
-
MODCLUSTER-731 Adding a non-started context should register the context in stopped stage
- Resolved
- relates to
-
UNDERTOW-1883 Enable mod_cluster proxy to register apps in stopped or disabled state
- Resolved