]
Brian Stansberry commented on WFLY-12356:
-----------------------------------------
I'm going to move this to WFCORE as that's where the remoting subsystem is.
remoting subsystem's http-connector is missing capability
reference
-------------------------------------------------------------------
Key: WFLY-12356
URL:
https://issues.redhat.com/browse/WFLY-12356
Project: WildFly
Issue Type: Bug
Components: Remoting
Affects Versions: 17.0.1.Final
Reporter: Radoslav Husar
Assignee: Ranabir Chakraborty
Priority: Major
Labels: ux
http-remoting-connector is missing capability reference to the undertow connector.
{noformat}
[standalone@localhost:9990 /]
/subsystem=remoting/http-connector=http-remoting-connector:write-attribute(name=connector-ref,value=foo)
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
{noformat}
results in a cryptic error
{noformat}
11:33:01,792 INFO [org.jboss.as.controller] (management-handler-thread - 1) WFLYCTL0183:
Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.remoting.remotingConnectorInfoService.http-remoting-connector
(missing) dependents: [service
org.wildfly.clustering.cache.registry-entry.ejb.client-mappings, service
org.wildfly.ejb.remote]
WFLYCTL0448: 5 additional services are down due to their dependencies being missing or
failed
11:33:15,334 INFO [org.jboss.as.controller] (management-handler-thread - 1) WFLYCTL0183:
Service status report
WFLYCTL0185: Newly corrected services:
service jboss.ejb.association (new available)
service jboss.ejb.remoting.connector.client-mappings (new available)
service jboss.remoting.remotingConnectorInfoService.http-remoting-connector (no
longer required)
service org.wildfly.clustering.cache.registry-entry.ejb.client-mappings (new
available)
service org.wildfly.clustering.cache.registry-factory.ejb.client-mappings (new
available)
service org.wildfly.clustering.group.ejb (new available)
{noformat}