[ 
https://issues.apache.org/jira/browse/SM-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14039109#comment-14039109
 ] 

Krzysztof Sobkowiak edited comment on SM-2335 at 6/20/14 6:03 PM:
------------------------------------------------------------------

I tired to install the features in order described by Gregor and my ServiceMix 
hang too. As it is a problem in PAX Web and we will not upgrade it in Karaf 
2.3.x it looks like we can not solve this problem (like SM-2287). Because we 
have a workaround with proper order of the features I think, we are not able to 
do something more with this problem.


was (Author: sobkowiak):
I tired ti install the features in order described by Gregor and my ServiceMix 
hang too. As it is a problem in PAX Web and we will not upgrade it in Karaf 
2.3.x it looks like we can not solve this problem (like SM-2287). Because we 
have a workaround with proper order of the features I think, we are not able to 
do something more with this problem.

> installing both webconsole and activemq-web-console causes hang
> ---------------------------------------------------------------
>
>                 Key: SM-2335
>                 URL: https://issues.apache.org/jira/browse/SM-2335
>             Project: ServiceMix
>          Issue Type: Bug
>    Affects Versions: 5.0.0
>            Reporter: Joeri Hendrickx
>             Fix For: 5.0.3, 5.1.1
>
>
> Hi,
> I've been having issues with Servicemix hanging;  after a lot of digging, I 
> eventually managed to reproduce it with a fixed scenario:
> Install a clean, fresh, servicemix 5.  Start it, and log into the shell.
> Then install the features (in this order):
> - webconsole
> - activemq
> - activemq-web-console
> At this point; one of two things happens.  Either you get an exception 
> (java.lang.NoClassDefFoundError: org/osgi/service/event/EventAdmin) but the 
> console will work; or it will display: Refreshing bundles 
> org.ops4j.pax.web.pax-web-extender-war (186), 
> org.ops4j.pax.web.pax-web-runtime (139) and then hang forever.
> When I encounter this; the instance can no longer be shut down cleanly.  
> If I kill it and then start it again, sometimes it will deadlock on startup.  
> Sometimes the amq console works, but it is still listed as 'uninstalled' in 
> the features.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to