[
https://issues.jboss.org/browse/WFLY-4401?page=com.atlassian.jira.plugin....
]
Thomas Diesler commented on WFLY-4401:
--------------------------------------
Yes, it is relate to the same race. The management endpoint becomes available while the
services it relies on are still starting up. IMHO, there should be a notion on
BOOTSTRAP_COMPLETE that is a prerequisite for client connectors to become available.
Deployment fails with missing/unavailable dependencies
------------------------------------------------------
Key: WFLY-4401
URL:
https://issues.jboss.org/browse/WFLY-4401
Project: WildFly
Issue Type: Bug
Components: Domain Management
Affects Versions: 8.2.0.Final
Reporter: Thomas Diesler
Assignee: Brian Stansberry
Our testsuite bootstraps the server and then waits for the native management interface to
become available on 8181
A subsequent deployment (intermittently) fails with
{code}
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
{code}
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
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)