[ https://issues.jboss.org/browse/JBAS-9010?page=com.atlassian.jira.plugin.... ] David Lloyd updated JBAS-9010: ------------------------------ Description: 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. was: When a deployment unit's ACTIVE service set is either fully installed, a deployment complete message is printed. When this service set consists of zero or more fully installed services, where each of the remaining services in the set possess one or more of the following traits: # Has missing dependency # Has failed dependency # Is failed 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. Complexity: Medium -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBAS-9010?page=com.atlassian.jira.plugin.... ] jaikiran pai commented on JBAS-9010: ------------------------------------ I haven't yet familiarized myself with MSC and the service states, but isn't this an typo: {quote} the deployment is considered in error when: 1. All ACTIVE services in C are UP, or {quote} shouldn't it be: {quote} the deployment is considered in error when: 1. All ACTIVE services in C are DOWN, or {quote} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBAS-9010?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on JBAS-9010: -------------------------------------- I did some investigating into how MSC handles dependencyInstalled and dependencyUninstalled. Say we have services A and B where A depends on B. If I first add A a dependencyUninstalled() event will be sent to the listener. If I then add B two more events will be fired, dependencyInstalled() for A and serviceStarted() for B. All these events can run concurrently, so effectively they can occur in any order. This behaviour is problematic when detecting missing dependencies in a deployment. When the last serviceStarted() is run, we effectively have no way of knowing if missing dependencies are still missing, or if the installation of this final service satisfied the dependencies, and a dependencyInstalled() event is running concurrently. An additional complication is that dependencyInstalled() can appear to run before dependencyUninstalled(), although it is possible to work around this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBAS-9010?page=com.atlassian.jira.plugin.... ] David Lloyd resolved JBAS-9010. ------------------------------- Resolution: Done -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira