Re: Orderly shutting down services

[vetalok <ve...@gmail.com>]

Guys, 
Could you please help me to resolve problem with unexpected Karaf shutdown?
I was asked this question  here
<http://stackoverflow.com/questions/35288889/karaf-stops-unexpectedly>   but
it still not answered. Here is the question:
After upgrading Karaf from 2.2.11 to 4.0.3 with log4j2 support and running
load tests of our Karaf based application, Karaf unexpectedly starts
shutdown process. 
We increased most of memory options but it did not help. 
No info in logs - just "Stopping blueprint extender" and "Unregistering
bundles...". Above these messages there was debug info from my bundles. In
manifest files of our bundles old OSGI container is used
(org.osgi.framework;version="1.3.0"). This occurs only with load tests, for
single threaded scenarios there are no problems. 
Can one bundle that fails trigger whole framework to stop? 
Any ideas why Karaf 4.0.3 is not stable and where we need to investigate?



--
View this message in context: http://karaf.922171.n3.nabble.com/Orderly-shutting-down-services-tp4027336p4045447.html
Sent from the Karaf - User mailing list archive at Nabble.com.

Re: Orderly shutting down services

[ch...@kiffer.ltd.uk]

vetalok,

> Can one bundle that fails trigger whole framework to stop?

If it fails hard enough, yes.  In fact even if it calls System.exit() ...

Suggest you first investigate this as a general Java-application-crashes
problem, e.g. collect and analyse heap dumps (hprof files), run whole
process in debugger if feasible, etc. ...