You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Nickolay Martinov (JIRA)" <ji...@apache.org> on 2010/12/09 16:39:01 UTC

[jira] Updated: (SM-2026) ServiceMix does not start some components if some component failed during start

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

Nickolay Martinov updated SM-2026:
----------------------------------

    Attachment: ComponentRegistry.java.fix.patch

Added patch that logs errors if component failed and continues with other components.

> ServiceMix does not start some components if some component failed during start
> -------------------------------------------------------------------------------
>
>                 Key: SM-2026
>                 URL: https://issues.apache.org/jira/browse/SM-2026
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: servicemix-core
>    Affects Versions: 3.3
>            Reporter: Nickolay Martinov
>         Attachments: ComponentRegistry.java.fix.patch
>
>
> During cotainer start ServiceMix sequentially restores state of components. If any component fails then all other components that come after it are not started. This turnes container into unusable state. For example if we comment out <import resource="classpath:activemq.xml" /> in servicemix.xml and remove dependency of jndi bean on broker bean in jndi.xml then servicemix-wsn2005 will fail and half of other components will not start. ServiceMix have to handle failures during components start.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.