[jboss-jira] [JBoss JIRA] (WFLY-8555) WebToUndertow default-virtual-host remains unchanged after migration from web subsystem having defined default-virtual-server

Tomaz Cerar (JIRA) issues at jboss.org
Tue Apr 11 07:25:00 EDT 2017


     [ https://issues.jboss.org/browse/WFLY-8555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomaz Cerar moved JBEAP-10286 to WFLY-8555:
-------------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-8555  (was: JBEAP-10286)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: Web (Undertow)
                           (was: Migration)
                           (was: Web (Undertow))
    Affects Version/s: 11.0.0.Alpha1
                           (was: 7.1.0.DR16)


> WebToUndertow default-virtual-host remains unchanged after migration from web subsystem having defined default-virtual-server
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-8555
>                 URL: https://issues.jboss.org/browse/WFLY-8555
>             Project: WildFly
>          Issue Type: Bug
>          Components: Web (Undertow)
>    Affects Versions: 11.0.0.Alpha1
>            Reporter: Tomaz Cerar
>            Assignee: Tomaz Cerar
>            Priority: Blocker
>
> Thanks to [JBEAP-10033] and discussion at [JBEAP-10200] there was discovered issue related to virtual hosts migration which was hidden till now.
> When migrating web -> undertow for migrating virtual hosts. In web there is on subsystem level default-virtual-server option, which per description corresponds more to the one in undertow default-host option on server level and currently it is migrated to it. Still in Undertow there is also default-virtual-host at undertow subsystem level which stays unchanged.
> Now with capabilities implemented on Undertow subsystem it points out that it is actually invalid configuration as the default-virtual-host points to non existing host (in case of the original virtual server being named differently than default-host), resulting in server failing to start afterwards \[1\] without any migration warning shown.
> The migration operation should update both default-virtual-host at subsystem level and default-host at server level.
> As there is no migration warning and the resulting configuration causes server start to fail, marking as blocker.
> \[1\] 
> {noformat}
> 14:48:35,386 ERROR [org.jboss.as.controller] (management-handler-thread - 2) 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.
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the jboss-jira mailing list