Is there any segments of the camel route that aren't part of the completion time? Sometimes it can be deceiving when looking at it.. why not put camel debug statements into your flow to output the messages in various stages.. that's what I do sometimes...then it might help narrow it down... also, during a lengthy shutdown get a thread dump with jvisialvm and use the threadanalyzer plugin and look for a hold up in your stuff, camel or karaf code.
Was just thinking that may not have all been spelled out completely so just wantes to make sure you had the best options I can suggest. Ryan Ryan On Feb 12, 2014 1:46 AM, "Vinu Raj" <[email protected]> wrote: > Agree to the fact that stop delay could be because of in flight messages. > But > I have a completionTimeout set for 3 minutes, but stop sometimes takes > 10-20 > minutes. I will do some more investigation on this and come back. > > > > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/Camel-routes-taking-time-to-start-stop-in-Karaf-3-0-0-tp4031593p4031620.html > Sent from the Karaf - User mailing list archive at Nabble.com. >
