Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-8555

WebToUndertow default-virtual-host remains unchanged after migration from web subsystem having defined default-virtual-server

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 11.0.0.Beta1
    • 11.0.0.Alpha1
    • Web (Undertow)
    • None
    • Hide

      call migrate operation on web subsystem looking like this:

          <subsystem xmlns="urn:jboss:domain:web:2.2" default-virtual-server="default" native="false">
      <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http"/>
      <virtual-server name="default" enable-welcome-root="true">
          <alias name="localhost"/>
          <alias name="example.com"/>
      </virtual-server>

</subsystem>
      Show
      call migrate operation on web subsystem looking like this: <subsystem xmlns="urn:jboss:domain:web:2.2" default-virtual-server="default" native="false"> <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http"/> <virtual-server name="default" enable-welcome-root="true"> <alias name="localhost"/> <alias name="example.com"/> </virtual-server> </subsystem>

    Description

      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] 

      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.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-10210 WebToUndertow default-virtual-host remains unchanged after migration from web subsystem having defined default-virtual-server

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Activity

            People

              tomazcerar Tomaž Cerar (Inactive)
              tomazcerar Tomaž Cerar (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: