[jboss-jira] [JBoss JIRA] (AS7-5222) Insufficient log info for failed deployments
[
https://issues.jboss.org/browse/AS7-5222?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler commented on AS7-5222:
-------------------------------------
I found this in ServiceVerificationHandler
// Record that unknown transitive dependencies are missing.
// TODO this is uninformative so not very nice, but MSC provides no
hooks to track from
// a ServiceController back to a missing/failed transitive dependency
or from a failed
// dependency down its dependents tree to this service. If that ever
changes, update
// this to make use of it
Insufficient log info for failed deployments
--------------------------------------------
Key: AS7-5222
URL: https://issues.jboss.org/browse/AS7-5222
Project: Application Server 7
Issue Type: Bug
Components: Server
Reporter: Thomas Diesler
Assignee: Jason Greene
Fix For: 7.2.0.Alpha1
I have a deployment that fails with
{code}
12:06:25,717 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS015870:
Deploy of deployment "example-webapp.wab" was rolled back with failure message
{"JBAS014771: Services with missing/unavailable dependencies" =>
["jboss.deployment.unit.\"example-webapp.wab\".REGISTER Missing[JBAS014861:
<one or more transitive dependencies>]"]}
12:06:25,737 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877:
Stopped deployment example-webapp.wab in 18ms
{code}
It doesn't say which dependencies are missing
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira