You shpuld have seen something in the debug.. I would tend to agree with JB.. most likely an inflight message.. maybe being sent asynchronously with no timeout? I'm guessing that could do it.
If you truly don't see anything in the debug messages, then you could get a stack dump to see what the threads are doing.. or camel has a mechanism to monitor which exchanges are where. I'd think the stack trace would be most beneficial. Ryan On Feb 10, 2014 7:24 AM, "Jean-Baptiste Onofré" <j...@nanthrax.net> wrote: > Hi Vinu, > > for the stop, it could be some inflight messages in the routes. For the > start, it's weird. > When you say starting route, it's just camel:route-start or > features:install (which download artifacts) ? > > Regards > JB > > On 02/10/2014 10:17 AM, Vinu Raj wrote: > >> I having camel routes consuming files deployed in Apache Karaf (3.0.0). >> Some >> times start/stop is very fast taking less than a seconds, but at times it >> is >> taking 15-20 minutes to for the camel context to start up or shut down. >> Enabled debug and checked, didn't get any clue. >> >> regards >> Vinu >> >> >> >> -- >> View this message in context: http://karaf.922171.n3.nabble. >> com/Camel-routes-taking-time-to-start-stop-in-Karaf-3-0-0-tp4031593.html >> Sent from the Karaf - User mailing list archive at Nabble.com. >> >> > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com >
