[CAMEL-7885] Timer - Restarting a timer endpoint may not trigger at expected time the first time

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.12.4, 2.13.2, 2.14.0
• Fix Version/s: 2.12.5, 2.13.3, 2.14.1, 2.15.0
• Component/s: camel-core
• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: Claus Ibsen
• Created: 01/Oct/14 07:40
• Updated: 01/Oct/14 09:19
• Resolved: 01/Oct/14 09:19

Description

If you stop a timer route, and that route has an inflight exchange causing the stop route to force stop due timeout. Then that timer task is still running in the background.

And if you restart the timer route, then it will reuse the old timer instance, which may be still running, and therefore the first trigger time may not happen at the time you would expect.

For example from timer:foo?period=2s to trigger every 2s.