Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-6425

Domain testsuite uses invalid remoting configuration

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 21.1.0.Final
    • 21.1.0.Beta2
    • Test Suite
    • None

      In the domain testsuite, several of the domain xml files use the following remoting configuration:

                  <subsystem xmlns="urn:jboss:domain:remoting:4.0">
                      <http-connector name="http-remoting-connector" connector-ref="default" sasl-authentication-factory="application-sasl-authentication"/>
                  </subsystem>
      

      However, this requires a HTTP upgrade registry supplied by an Undertow listener not provided by the configuration.

      This causes the following errors on every server boot:

      08:49:21,930 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
          ("subsystem" => "remoting"),
          ("http-connector" => "http-remoting-connector")
      ]) - failure description: {
          "WFLYCTL0412: Required services that are not installed:" => ["jboss.http-upgrade-registry.default"],
          "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.remoting.remoting-http-upgrade-service.http-remoting-connector is missing [jboss.http-upgrade-registry.default]"]
      }
      08:49:21,937 INFO  [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
      WFLYCTL0184:    New missing/unsatisfied dependencies:
            service jboss.http-upgrade-registry.default (missing) dependents: [service jboss.remoting.remoting-http-upgrade-service.http-remoting-connector] 
      

      Switching these configurations to use a standard remoting connector resolves the problem.

            pferraro@redhat.com Paul Ferraro
            pferraro@redhat.com Paul Ferraro
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: