We have encountered an issue with the Camel timer. We have a bean that starts/stops the route where the timer is defined. It works pretty well while the route is shutdown successfully and no exchange is inflight.
However, if the bean stops the route while the exchange is still inflight, Camel will wait 300 seconds.

If, for some reasons, the exchange couldn’t be completed after 300 seconds, the DefaultShutdownStrategy will force a shutdown. Then the issue happens when the bean restarts the route.

The timer is configured to trigger an event every 2 seconds. However, after restart, it sometimes waits much longer to trigger the first event. But all subsequent triggers would work fine.

Please see attached test case for more detail.