karaf-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ryan Moquin <fragility...@gmail.com>
Subject Re: Issues with latest Karaf 2.3.1
Date Wed, 06 Mar 2013 02:50:48 GMT
I think if a bundle fails to start correctly, Karaf remembers that on next
startup (I think, for some reason I thought I noticed that).  Regardless,
if one of your bundles is being stopped, then it probably errored out and
maybe it's managed to clog up a thread karaf has to wait on to terminate.
You really need to see if there are any errors in your log, or dump the
thread states and look for a thread that references your code.... that
might help.

On Mar 5, 2013 5:37 AM, "djos06" <djos06@gmail.com> wrote:

> 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.

View raw message