I have an application using the Quartz Scheduler to schedule jobs. The application is currently running Quartz version 1.6.2. My JobStore is org.quartz.impl.jdbcjobstore.JobStoreTX with an Oracle database. Clustering is turned on, but there's only one scheduler using the database.
When my thread pool is maxed out, and new jobs get triggered, the jobs seem to go into some kind of waiting state. When a new thread opens up, the jobs that missed their fire time get fired, but the scheduler seems to choose which waiting job to fire somewhat randomly. A job that's been waiting 5 minutes might get fired before the job that's been waiting for 8 hours.
Is it possible to make my waiting jobs get fired in the order they were triggered?