I have a weekly data export that uses a quart timer defined like this: quartz://circVendorRoyaltyTimer?cron=0+0+1+?+*+SAT+*
The timer sends a message to a route that in turn sends a message with a date range in it to another route that queries the data based on that date range and then puts the results in a queue. This was done so that the default behavior would be a timed export, but we can manually export different date ranges and suspend the timer route for testing while leaving the manual export enabled. Early last Friday, I deployed a new version of this and then used JMX to suspend the timer. I then sent the message to trigger a manual export at 1:13am on Saturday. The export processing is done by a system on the other side of the country, so it wasn't until this morning that I found out that there were two exports done: - one at 1:00am - one at 1:13am I double checked the timer this morning, it's stopped. I think my question is: Does the quartz component schedule the job proactively when it starts, or is it somehow waiting for the time to arrive, then running it at that time? Based on the outcome of my export, I'm guessing the former. If that's true, is there a way to cancel that scheduled job? Larry
