I also had the problem that karaf can take a long time to shut down.
Till now I have not digged deeper into the problem.
Typicall it happens if an Activator does not return when stopping a
bundle. This can have a lot of reasons though.
Any ideas how to debug this?
Perhaps we could support this by printing the bundles that can not be
stopped in the log.
I also can reproduce the problem that when karaf is killed not all
bundles come back up again. I guess the state of the bundles is
persisted and
reflects the status when karaf was killed.
Christian
Am 05.03.2013 11:37, schrieb djos06:
Hi,
I was hoping that the latest version of Karaf could correct my bug but it
doesn't.
I explain myself :
Sometimes, I try to shutdown karaf properly via stop script and most of the
times it never succeed to stop it, so i have to kill karaf process.
When I start karaf again, my bundles doesn't starts, there is always one
bundle which is stopping and others are in grace period or creating. And it
is sucked like this...
It seems karaf keep bundle state for some of them but not all, especially
for the one which is 'stopping'.
Do you know what is the problem here ?
is there a way to correct it ?
is it a bug of karaf ?
Thanks
Nicolas
--
View this message in context:
http://karaf.922171.n3.nabble.com/Issues-with-latest-Karaf-2-3-1-tp4028022.html
Sent from the Karaf - User mailing list archive at Nabble.com.
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
