]
Jason Greene updated AS7-546:
-----------------------------
Moving all non-critical issues to the CR. If you finish it before we release beta please
correct the fix-for version.
Thanks
handling of service start failure
---------------------------------
Key: AS7-546
URL:
https://issues.jboss.org/browse/AS7-546
Project: Application Server 7
Issue Type: Sub-task
Reporter: Alexey Loubyansky
Assignee: John Bailey
Fix For: 7.1.0.CR1
In this case, the exception is logged, and all the service's dependents will be
trapped in a waiting state. This type of error will typically be due to transient
conditions, like an incorrectly configured IP address, disk space issues, and so on. The
correct behavior here is to log the error and let the user decide (based on the GUI or
perhaps by deployment plan policy) whether to fix the issue and retry the failed service,
let the error stand, or pull out the deployment unit.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: