Missing http-remoting-connector after upgrade to Wildfly 21

Artur Socha

unread,

Dec 7, 2020, 11:21:15 AM12/7/20

to WildFly

Hello,
I'm working on upgrading Wildfly from version 19 to 21 for ovirt-engine [1].
Most things work fine by default without configuration changes on WF19,WF20 & WF21.
However, on WF21 there is an issue related to http-remoting-connector.
Here is the error details:
2020-12-03 14:54:54,682+01 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]"]
}

2020-12-03 14:54:54,771+01 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]

We used to have it configured as:
    <subsystem xmlns="urn:jboss:domain:remoting:4.0">
      <endpoint worker="default"/>
      <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"/>
    </subsystem>

I (semi)blindly changed [2] connector-ref to 'https' which fixed the issue on my dev setup, but it fails on one of our scenarios when we use AJP with HTTPD as proxy (HTTPS enpoint is disabled).

I can, of course, create additional socket binding and use it as endpoint as it was done here [3].
That works but I would like to understand what really happened with connector-ref='default' that is no longer available in WF21.

My WF/Jboss configuration background is rather limited so I would like to ask you for any hints or recommendations how to deal with it.

thanks
Artur

[1] https://github.com/oVirt/ovirt-engine/
[2] https://github.com/oVirt/ovirt-engine/blob/master/packaging/services/ovirt-engine/ovirt-engine.xml.in#L543
[3] https://gerrit.ovirt.org/#/c/ovirt-engine/+/112505/1/packaging/services/ovirt-engine/ovirt-engine.xml.in

Giorgio Giustiniani

unread,

Sep 15, 2021, 10:28:53 AM9/15/21

to WildFly

Hi,

did you resolve?

Artur Socha

unread,

Sep 16, 2021, 2:32:20 AM9/16/21

to Giorgio Giustiniani, WildFly

Hi Giorgio,

It's hard to say whether I fixed it or not. Definitely I managed to work it around :) This patch [1] does exactly that.

[1] https://gerrit.ovirt.org/112505/

Artur

--
You received this message because you are subscribed to a topic in the Google Groups "WildFly" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/wildfly/4KaARRGJZ6c/unsubscribe.
To unsubscribe from this group and all its topics, send an email to wildfly+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/wildfly/39cedc3d-e819-4a7e-b9eb-7875f7ebe3a3n%40googlegroups.com.