]
David Lloyd reassigned JBAS-9010:
---------------------------------
Assignee: David Lloyd
Provide more comprehensive error messages for missing dependencies
------------------------------------------------------------------
Key: JBAS-9010
URL:
https://issues.jboss.org/browse/JBAS-9010
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: David Lloyd
Assignee: David Lloyd
Fix For: 7.0.0.Beta3
Given a set of services _C_ from a composite operation consisting of or containing one or
more deployment, and a set of services _D_ from a deployment installed within the
operation, the deployment is considered in error when:
# All ACTIVE services in _C_ are UP, or
# have one or more missing dependency, or
# have one or more failed dependency, or
# are themselves in a failed state
AND one or more services in _D_:
# have one or more missing dependency, or
# have one or more failed dependency, or
# are themselves in a failed state
Then a deployment shall be considered to be failed.
For each failed deployment, a failed message should be logged with a summary of the
problem. All missing dependencies should be associated with the applicable deployment
dependent(s) and listed. Services which are failed should be listed BUT not with the
failure cause or stack trace, which will have appeared in the log already.
Deployments that have failed will also cause the runtime portion of the operation to be
treated as failed; the deployment or server start operation handler may act on this
information as it would with any failed operation.
A failed deployment may become successful later on if a missing dependency is satisfied
as a result of another deployment being installed. A previously successful deployment may
enter a failed state if a required, satisfied dependency is later uninstalled. At the
conclusion of an operation which causes a previously successful deployment to be failed, a
message need not be logged however that can be considered for this or a later release.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: