Page History

...

Notice how it waits while there are inflight exchanges still being processed before it can shutdown.

Suppressing logging due to timeout not allowing all inflight messages to complete

Available as of Camel 2.13

If a graceful shutdown could not shutdown cleanly within the given timeout period, then Camel performs a more aggressive shutdown by forcing routes and thread pools etc to shutdown. And as well the routing engine will reject continue processing Exchanges. If this happens you may see WARN logs about Exchanges being rejected and other failures due the forced shutdown.

If you do not want to see these logs, you can suppress this by setting the option SuppressLoggingOnTimeout to true.

context.getShutdownStrategegy().setSuppressLoggingOnTimeout(true);

Notice the suppress is a "best effort" though there may still be some logs coming from 3rd party libraries and whatnot, which Camel cannot control.

Controlling ordering of routes

...