You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Jarek Gawor (JIRA)" <ji...@apache.org> on 2011/05/26 06:58:47 UTC

[jira] [Assigned] (GERONIMO-5963) Keep bundles around if EBA start failed

     [ https://issues.apache.org/jira/browse/GERONIMO-5963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jarek Gawor reassigned GERONIMO-5963:
-------------------------------------

    Assignee: Jarek Gawor

> 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
>
> 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