[
https://issues.apache.org/jira/browse/GERONIMO-5963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13039791#comment-13039791
]
Jarek Gawor commented on GERONIMO-5963:
---------------------------------------
In revision 1127978 I updated the code not to throw an exception (i.e. fail the
deployment) when one of the bundles of the application fails to start. This
behavior can be changed to work like before by setting
"org.apache.geronimo.aries.failApplicationOnStartError" system property to
"true".
> Keep bundles around if EBA start failed
> ---------------------------------------
>
> Key: GERONIMO-5963
> URL: https://issues.apache.org/jira/browse/GERONIMO-5963
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Aries
> Affects Versions: 3.0
> Reporter: Jarek Gawor
> Assignee: Jarek Gawor
> Fix For: 3.0
>
>
> If EBA fails to start - i.e. one of the bundles within the EBA fails to
> start, right all, all the EBA bundles will be uninstalled and removed from
> the framework. This gives no chance whatsoever to diagnose the start up
> problem. If would be good to at least have an option control what happens
> when EBA start up fails.
> Maybe even we should change the current default to not to fail the EBA. All
> the bundles are in fact installed ok but some of them failed to start. That
> should mean that EBA is deployed ok but failed to start.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
