servicemix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] Updated: (SM-2026) ServiceMix does not start some components if some component failed during start
Date Thu, 17 Feb 2011 19:46:24 GMT

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

Jean-Baptiste Onofré updated SM-2026:
-------------------------------------

    Fix Version/s: 3.3.3

> 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
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 3.3.3
>
>         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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message