Without knowing much about your application (you didn't tell much about the way it's set-up), but my gut-feeling tells me it's your bundle that's buggy. How does it work, is it using a Activator? Do you do some special handling in the stop method? Or do you use blueprint. I'd say try to strip down your application to a minimum to find the issue.
regards, Achim 2013/3/5 djos06 <[email protected]> > 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. > -- Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project Lead blog <http://notizblog.nierbeck.de/>
