When Camel hit that timeout, it asks the JDK to forcibly shutdown its threads now. And if the JDK takes time to do this, then that timetask still be running, and thus show a negative value.
We could maybe improve the log message to not go negative, but show sometime about forcibly shutting down, and waiting for the JVM to terminate the threads. Fell free to create a JIRA to have the log message improved. On Mon, May 9, 2011 at 4:28 PM, Tom Howe <[email protected]> wrote: > 2.7.0 > > On Mon, May 9, 2011 at 3:06 PM, Claus Ibsen <[email protected]> wrote: > >> What version of Camel do you use? >> >> -- >> Claus Ibsen >> ----------------- >> FuseSource >> Email: [email protected] >> Web: http://fusesource.com >> CamelOne 2011: http://fusesource.com/camelone2011/ >> Twitter: davsclaus >> Blog: http://davsclaus.blogspot.com/ >> Author of Camel in Action: http://www.manning.com/ibsen/ >> > -- Claus Ibsen ----------------- FuseSource Email: [email protected] Web: http://fusesource.com CamelOne 2011: http://fusesource.com/camelone2011/ Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
