You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Charles Moulliard (JIRA)" <ji...@apache.org> on 2008/12/01 10:21:05 UTC
[jira] Created: (SMX4KNL-153) Stoping one of the "core" bundles of
the servicemix engine block the server
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.
[jira] Assigned: (SMX4KNL-153) Stopping one of the "core" bundles
of the servicemix engine block the server
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4KNL-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet reassigned SMX4KNL-153:
---------------------------------------
Assignee: Guillaume Nodet
> 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
> Assignee: Guillaume Nodet
> 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.
[jira] Updated: (SMX4KNL-153) Stopping one of the "core" bundles of
the servicemix engine block the server
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4KNL-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet updated SMX4KNL-153:
------------------------------------
Fix Version/s: (was: 1.1.0)
> 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.
[jira] Commented: (SMX4KNL-153) Stoping one of the "core" bundles
of the servicemix engine block the server
Posted by "Charles Moulliard (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4KNL-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47735#action_47735 ]
Charles Moulliard commented on SMX4KNL-153:
-------------------------------------------
Guillaume,
Why, don't we put the core "bundles" in a separate instance of the Kernel ?
or
Why don't we define security access to govern access rights for administrator to "core bundles" ?
> 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.
[jira] Resolved: (SMX4KNL-153) Stopping one of the "core" bundles
of the servicemix engine block the server
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4KNL-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet resolved SMX4KNL-153.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.1.0
Sending assembly/src/main/filtered-resources/etc/startup.properties
Sending gshell/gshell-admin/src/main/filtered-resources/org/apache/servicemix/kernel/gshell/admin/etc/startup.properties
Sending gshell/gshell-osgi/src/main/java/org/apache/servicemix/kernel/gshell/osgi/BundleCommand.java
Sending gshell/gshell-osgi/src/main/java/org/apache/servicemix/kernel/gshell/osgi/BundleLevel.java
Sending gshell/gshell-osgi/src/main/java/org/apache/servicemix/kernel/gshell/osgi/ListBundles.java
Transmitting file data .....
Committed revision 736254.
> 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
> Assignee: Guillaume Nodet
> Fix For: 1.1.0
>
> 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.
[jira] Commented: (SMX4KNL-153) Stopping one of the "core" bundles
of the servicemix engine block the server
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4KNL-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48667#action_48667 ]
Guillaume Nodet commented on SMX4KNL-153:
-----------------------------------------
Good point, and yeah, it makes perfect sense to me.
> 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.
[jira] Updated: (SMX4KNL-153) Stopping one of the "core" bundles of
the servicemix engine block the server
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (SMX4KNL-153) Stopping one of the "core" bundles of
the servicemix engine block the server
Posted by "Jamie Goodyear (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (SMX4KNL-153) Stoping one of the "core" bundles
of the servicemix engine block the server
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4KNL-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48464#action_48464 ]
Guillaume Nodet commented on SMX4KNL-153:
-----------------------------------------
Not sure what you mean by a "separate" instance of the kernel: there is a single osgi framework running and the shell is inside this osgi framework, else we would not be able to easily access the osgi layer.
I'd rather investigate the second way, i.e. using security, but this would mean associating each bundle with certain priviledges. While securing commands should be easily doable, I'm not sure if this is possible to secure bundles with different permissions. Another way would be to check the start-level of the bundle: user bundles should be installed at level >= 50, and core bundles installed at level < 50. We would rely on this information to know if the bundle being modified is a core bundle or a user bundle and require different roles.
Of course, it would first require to have a role based security framework, which we don't really have yet (at least for commands).
> 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.
[jira] Commented: (SMX4KNL-153) Stoping one of the "core" bundles
of the servicemix engine block the server
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4KNL-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48465#action_48465 ]
Guillaume Nodet commented on SMX4KNL-153:
-----------------------------------------
A first step could be to ask a confirmation for bundles with a start-level < 50.
> 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.
[jira] Updated: (SMX4KNL-153) Stopping one of the "core" bundles of
the servicemix engine block the server
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4KNL-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet updated SMX4KNL-153:
------------------------------------
Summary: Stopping one of the "core" bundles of the servicemix engine block the server (was: Stoping one of the "core" bundles of the servicemix engine block the server)
> 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
>
>
> 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.
[jira] Commented: (SMX4KNL-153) Stopping one of the "core" bundles
of the servicemix engine block the server
Posted by "Charles Moulliard (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4KNL-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48719#action_48719 ]
Charles Moulliard commented on SMX4KNL-153:
-------------------------------------------
@All,
Many thanks for the improvements added to ServiceMix Kernel.
> 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.
[jira] Commented: (SMX4KNL-153) Stopping one of the "core" bundles
of the servicemix engine block the server
Posted by "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.
[jira] Updated: (SMX4KNL-153) Stopping one of the "core" bundles of
the servicemix engine block the server
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMX4KNL-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet updated SMX4KNL-153:
------------------------------------
Fix Version/s: (was: 1.0.1)
1.1.0
> 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.1.0
>
> 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.
[jira] Commented: (SMX4KNL-153) Stoping one of the "core" bundles
of the servicemix engine block the server
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ 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.