[
https://issues.apache.org/activemq/browse/SMX4-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54474#action_54474
]
Willem Jiang commented on SMX4-376:
-----------------------------------
@ Guillaume,
I found the
https://svn.apache.org/repos/asf/servicemix/smx4/specs/trunk/locator/src/main/java/org/apache/servicemix/specs/locator/Activator.java
also does the same thing as the Camel osgi activator used to.
I think we need to give the servicemix specs locator activator same change to
avoid the servicemix hang.
> restart karaf container in servicemix kit will hang
> ---------------------------------------------------
>
> Key: SMX4-376
> URL: https://issues.apache.org/activemq/browse/SMX4-376
> Project: ServiceMix 4
> Issue Type: Bug
> Reporter: Freeman Fang
> Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>
> first we start karaf in features kit, all is fine
> but if we do osgi:shutdown and restart the karaf, the karaf will hang
> in the log, it stop at
> 17:21:23,486 | INFO | pool-2-thread-2 | SecurityUtils |
> e.sshd.common.util.SecurityUtils 80 | BouncyCastle not registered, using
> the default JCE provider
> 17:21:25,347 | INFO | FelixStartLevel | Activator |
> org.apache.camel.osgi.Activator 170 | Camel activator starting
> in the console, we input osgi:list, but only response
> START LEVEL 100
> then no more response
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
