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

["Jamie Goodyear (JIRA)" <ji...@apache.org>]

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

Jamie Goodyear commented on SMX4KNL-153:
----------------------------------------

I like the idea of asking a confirmation for bundles with a start-level < 50, should we also add a confirmation for when we modify a bundle bringing it down to under 50?

ex:

{noformat}
servicemix osgi > list
ID   State          Spring     Level  Name
...
[39] [Active     ] [       ] [   100]  some bundle

servicemix osgi > bundle-level 39 25
You are about to designate bundle as a system bundle.  Do you want to continue (yes/no): yes
{noformat}


> Stopping 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
>         Attachments: SMX4KNL-153.patch
>
>
> 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.