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, a
2.7.0
On Mon, May 9, 2011 at 3:06 PM, Claus Ibsen wrote:
> What version of Camel do you use?
>
> --
> Claus Ibsen
> -
> FuseSource
> Email: cib...@fusesource.com
> Web: http://fusesource.com
> CamelOne 2011: http://fusesource.com/camelone2011/
> Twitter: davsclaus
> Blog: http://
What version of Camel do you use?
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
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/
Why does camel not actually timeout at 0 when shutting down?
@40004dc7f43516839684 2011-05-09 15:03:23,377 [Camel (mrs) thread #31 -
ShutdownTask] INFO org.apache.camel.impl.DefaultShutdownStrategy - Waiting
as there are still 1 inflight and pending exchanges to complete, timeout in
4 second
