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

[jira] Commented: (SMX4KNL-153) Stoping one of the "core" bundles of the servicemix engine block the server

    [ https://issues.apache.org/activemq/browse/SMX4KNL-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47734#action_47734 ] 

Guillaume Nodet commented on SMX4KNL-153:
-----------------------------------------

This is because the "core" bundles are used by the console itself.  I'm not sure if there is any workaround about that.
We might be able to issue a warning to the user when a bundle referenced by the console is stopped, or maybe make sure that updating those bundle work (it might be doable), but not much more afaik.

> Stoping one of the "core" bundles of the servicemix engine block the server
> ---------------------------------------------------------------------------
>
>                 Key: SMX4KNL-153
>                 URL: https://issues.apache.org/activemq/browse/SMX4KNL-153
>             Project: ServiceMix Kernel
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>            Reporter: Charles Moulliard
>             Fix For: 1.0.1
>
>
> Hi,
> I have discovered a strange behavior of the application. It is possible to stop one of the "core" bundle of ServiceMix Kernel. In consequence, the server is blocked and the java process must be killed !
> ex : servicemix osgi > stop 14 (correspond to Spring OSGI extender)
> KR,
> Charles Moulliard
> SOA Architect
> Xpectis

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