[
https://issues.apache.org/activemq/browse/SMX4KNL-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jamie Goodyear updated SMX4KNL-153:
-----------------------------------
Attachment: SMX4KNL-153-bl.patch
Attachment: SMX4KNL-153-bl.patch
Added some validation code to osgi Bundle-Level command to prompt users if
they are sure that they want to designate a bundle as a system bundle
(level<50).
Will not prompt user if modifying from level under 50 to another level under
50 - user will have already be prompted that they are modifying a system bundle.
> 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-bl.patch, 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.
