[
https://issues.jboss.org/browse/WFLY-10188?page=com.atlassian.jira.plugin...
]
Brian Stansberry commented on WFLY-10188:
-----------------------------------------
[~swd847] Sorry; I didn't see this. That sounds reasonable, particularly if it was
impossible (or at least quite hard) to configure a working server via the CLI in a manner
that would now break. Without thinking hard the only way I think that would happen was if
CLI scripts were used to recreate our existing standard configuration and the script did
not set the attributes.
Setting Undertow default server needs validation of provided server
to avoid broken Wildfly configuration
---------------------------------------------------------------------------------------------------------
Key: WFLY-10188
URL:
https://issues.jboss.org/browse/WFLY-10188
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 14.0.1.Final, 12.0.0.Final, 13.0.0.Final
Reporter: Pavel Jelinek
Assignee: Stuart Douglas
Priority: Critical
Undertow server needs default-host to be set to be able to be used as Undertow subsystem
default-server otherwise Wildfly would not start due to:
{code}
ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities
required by resource '/subsystem=undertow' are not available:
org.wildfly.undertow.host.test-server.default-host; Possible registration points for
this capability:
/subsystem=undertow/server=*/host=*
{code}
This is dangerous as after calling a {{reload}} operation, the server simply fails and
crashes. One can accidentaly kill the server with this and \!manual\! fix is necessary to
the configuration to be able to start server again.
I think that there should be some check that configuration of the newly created server is
complete and valid before it is set as a default server.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)