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-2118) Container is in inconsistent state just after start
Date Thu, 01 Sep 2011 07:58:10 GMT

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

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

    Fix Version/s: 3.4

> Container is in inconsistent state just after start
> ---------------------------------------------------
>
>                 Key: SM-2118
>                 URL: https://issues.apache.org/jira/browse/SM-2118
>             Project: ServiceMix
>          Issue Type: Improvement
>          Components: servicemix-core
>    Affects Versions: 3.3.2
>         Environment: Linux, HP-UX, jdk6
>            Reporter: Nickolay Martinov
>            Assignee: Jean-Baptiste Onofré
>              Labels: patch
>             Fix For: 3.4
>
>         Attachments: servicemix-core-wait-for-smx-to-finish-starting.patch
>
>
> Start script returns control just after java process was launched. But components and
service assemblies that were previously installed/deployed will continue to be loaded/initialized
in background. This process may time few seconds but in reality when large number of components
and SAs were previously deployed it may take minutes on busy server. If container was started
by some script and then this script does something with container (like checking state of
components and SAs, deploying things, etc) it is very likely to fail. Instead smx start script
should hold control until container actually finishes starting up or time outs.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message