FWIW, I've put together a really basic page that evaluates cron expressions using Quartz.Net's CronExpression class. It's pretty basic but it catches things like these. Input a cron expression and see the next 10 fire times: A CRON expression is a string comprising 5 fields separated by white space that represents a set of times, normally as a schedule to execute some routine. Format * in the value field above means all legal values as in braces for that column. The value column can have a * or a list of elements … Continued
In that configuration the poster would get the behavior they observed: The job will run once per minute during hours that are evenly divisible by 4. To avoid running once per minute a number is needed in the first column, like this: 15 * * * * whatever... That will run on the 15th minute after every hour. Clearly the intent of the first cron expression is to run a job every 2 1/2 hours, but it actually isn't possible to express that using a cron expression, and since the invalid interval gets ignored, the job actually runs every hour.
Walton samuel grayson
Mazak programming examples
Atomic basics worksheet answers key
Forever 21 credit card