-
Bug
-
Resolution: Done
-
Blocker
-
None
-
7.1.0.DR16
The capabilities update done by JBEAP-10033 expects that there is always host named default-host even though it is valid to use different name.
Due this the server fails to start with [1]. The undertow subsystem configuration with just changed the name for host + default-host reference may look like this [2].
[1]
11:22:59,388 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=undertow' are not available:
org.wildfly.undertow.host.default-server.default-host; There are no known registration points which can provide this capability.
[2]
<subsystem xmlns="urn:jboss:domain:undertow:4.0">
<buffer-cache name="default"/>
<server name="default-server" default-host="default">
<http-listener name="default" socket-binding="http" redirect-socket="https" enable-http2=
<https-listener name="https" socket-binding="https" security-realm="ApplicationRealm" ena
<host name="default" alias="localhost">
<location name="/" handler="welcome-content"/>
<filter-ref name="server-header"/>
<filter-ref name="x-powered-by-header"/>
</host>
</server>
<servlet-container name="default">
<jsp-config/>
<websockets/>
</servlet-container>
<handlers>
<file name="welcome-content" path="${jboss.home.dir}/welcome-content"/>
</handlers>
<filters>
<response-header name="server-header" header-name="Server" header-value="JBoss-EAP/7"/>
<response-header name="x-powered-by-header" header-name="X-Powered-By" header-value="Unde
</filters>
</subsystem>
- is caused by
-
-
- Closed
-
- is related to
-
WFLY-8538 Remove need to configure default-virtual-host at subsystem level
-
- Open
-
