[
https://issues.apache.org/activemq/browse/SMX4KNL-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated SMX4KNL-153:
------------------------------------
Attachment: SMX4KNL-153.patch
The patch implements a possible "solution" : prompting the user for a
confirmation when modifying a bundle with a start level < 50.
The patch also modifies the default start level of core bundles.
Actually, changing the start level of gshell-core from 100 to 50 might be a
problem in some cases, because commands passed on the command line may start
before all the user bundles are installed and started.
> 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
> Fix For: 1.0.1
>
> 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.
