Try googling for "java thread dump" and you'll find the answer. On Tue, Jun 30, 2009 at 13:50, Charles Moulliard<cmoulli...@gmail.com> wrote: > How can I achieve this ? > > Charles Moulliard > Senior Enterprise Architect > Apache Camel Committer > > ***************************** > blog : http://cmoulliard.blogspot.com > > > On Tue, Jun 30, 2009 at 1:42 PM, Guillaume Nodet <gno...@gmail.com> wrote: > >> Could you grab a thread dump of the vm when the shutdown is waiting ? >> There must be a deadlock somewhere but without any thread dump, it's >> kinda impossible to see what happen. >> >> On Tue, Jun 30, 2009 at 13:25, Charles Moulliard<cmoulli...@gmail.com> >> wrote: >> > Hi, >> > >> > When Camel tries to stop one of its context, the following message is >> > displayed in the log: >> > >> > 13:10:59,213 | INFO | Timer-2 | DefaultCamelContext >> | >> > e.camel.impl.DefaultCamelContext 965 | Apache Camel 2.0-SNAPSHOT >> > (CamelContext:InToOut) is stopping >> > 13:11:00,244 | INFO | Timer-2 | DefaultCamelContext >> | >> > e.camel.impl.DefaultCamelContext 975 | Apache Camel 2.0-SNAPSHOT >> > (CamelContext:InToOut) stopped >> > 13:11:00,244 | INFO | Timer-2 | DefaultCamelContext >> | >> > e.camel.impl.DefaultCamelContext 965 | Apache Camel 2.0-SNAPSHOT >> > (CamelContext:OutToIn) is stopping >> > *13:11:09,181 | ERROR | Thread-47 | RunnableTimedExecution >> > | oncurrent.RunnableTimedExecution 109 | Closing runnable for context >> > OsgiBundleXmlApplicationContext(bundle=com.xpectis.x3s.x3s-core, >> > config=osgibundle:/META-INF/spring/*.xml) did not finish in 10000ms; >> > consider taking a snapshot and then shutdown the VM in case the thread >> still >> > hangs >> > 13:11:19,181 | ERROR | Thread-47 | RunnableTimedExecution >> | >> > oncurrent.RunnableTimedExecution 109 | Closing runnable for context >> > OsgiBundleXmlApplicationContext(bundle=com.xpectis.x3s.x3s-service, >> > config=osgibundle:/META-INF/spring/*.xml) did not finish in 10000ms; >> > consider taking a snapshot and then shutdown the VM in case the thread >> still >> > hangs* >> > >> > It seems to be related to the following Spring DM error : >> > http://jira.springframework.org/browse/OSGI-611 but I use Spring OSGI >> 1.2 >> > and the error is still there >> > >> > Does anybody knows how to solve this ? >> > >> > Regards, >> > >> > Charles Moulliard >> > Senior Enterprise Architect >> > Apache Camel Committer >> > >> > ***************************** >> > blog : http://cmoulliard.blogspot.com >> > >> >> >> >> -- >> Cheers, >> Guillaume Nodet >> ------------------------ >> Blog: http://gnodet.blogspot.com/ >> ------------------------ >> Open Source SOA >> http://fusesource.com >> >
-- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
