-
Bug
-
Resolution: Done
-
Major
-
7.1.0.DR7
-
None
-
User Experience
-
-
-
-
-
-
When I set a management-access-predicate attribute in mod-cluster filter to some non-sense value and perform reload as requested, server prints following error in server.log:
11:18:13,442 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "ejb3")]) - failure description: { "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined, "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { "Services that were unable to start:" => [ "jboss.ejb.default-local-ejb-receiver-service", "jboss.ejb3.ejbClientContext.default", "jboss.ejb3.localEjbReceiver.value" ], "Services that may be the cause:" => [ "jboss.remoting.remotingConnectorInfoService.http-remoting-connector", "jboss.undertow", "jboss.web.common.server" ] } } 11:18:13,443 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "ejb3"), ("service" => "remote") ]) - failure description: { "WFLYCTL0412: Required services that are not installed:" => ["jboss.remoting.remotingConnectorInfoService.http-remoting-connector"], "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.ejb3.connector is missing [jboss.remoting.remotingConnectorInfoService.http-remoting-connector]"] } 11:18:13,443 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "webservices")]) - failure description: { "WFLYCTL0412: Required services that are not installed:" => [ "jboss.web.common.server", "jboss.undertow" ], "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.ws.config is missing [jboss.undertow, jboss.web.common.server]"] }
From that error it is very hard to see what is actually causing the problem. Only what I can see is that some of the subsystems probably did not started and I need to investigate.
It would be nice if either this error would point me more precisely to the badly set management-access-predicate attribute or (what would be probably even better) if I the operation when I tried to set that attribute with invalid value ended with error with appropriate message directly.
- is cloned by
-
WFLY-7565 Server provides very generic error when 'management-access-predicate' attribute is set badly
- Closed