-
Bug
-
Resolution: Obsolete
-
Major
-
None
-
None
-
None
Our testsuite bootstraps the server and then waits for the native management interface to become available on 8181
A subsequent deployment (intermittently) fails with
domain-master> [Host Controller] [0m[0m05:09:40,678 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014900: Content added at location /opt/jboss/wildfly/domain/data/content/ef/3743938a6b38a2ae473f12778fef7ad0ce464c/content[0m domain-slave> [Server:server-one] [0m[31m05:09:41,654 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 5) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "domain-endpoint.war")]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"domain-endpoint.war\" is missing [jboss.deployment.chains]"]}[0m
There seems to be a missing guarantee that allows the management endpoint to answer deployment requests when the deployment chain services are not up.
CrossLink: https://github.com/wildfly-extras/wildfly-camel/issues/175
- duplicates
-
WFCORE-184 Handle external requests during boot with a failure that indicates non-readiness
-
- Resolved
-
