Hello,
I copied/pasted your code in a unit test (using seconds instead of hours in the cron expressions and using 2 different sample job classes), using those properties for quartz.properties :
Code:
org.quartz.scheduler.instanceName: TestScheduler
org.quartz.scheduler.instanceId: AUTO
org.quartz.scheduler.skipUpdateCheck: true
org.quartz.threadPool.class: org.quartz.simpl.SimpleThreadPool
org.quartz.threadPool.threadCount: 3
org.quartz.threadPool.threadPriority: 5
org.quartz.jobStore.misfireThreshold: 60000
org.quartz.jobStore.class: org.quartz.simpl.RAMJobStore
and I got the expected output (using quartz 2.2) (sleeping for 10 seconds right after the scheduler.triggerJob( oneHRJob.getKey() );)
Code:
[INFO] 30 Jul 09:14:58.685 AM main [org.quartz.impl.StdSchedulerFactory]
Quartz scheduler 'TestScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
[INFO] 30 Jul 09:14:58.685 AM main [org.quartz.impl.StdSchedulerFactory]
Quartz scheduler version: 2.2.0-SNAPSHOT
Starting Scheduler
[INFO] 30 Jul 09:14:58.700 AM main [org.quartz.core.QuartzScheduler]
Scheduler TestScheduler_$_NON_CLUSTERED started.
Scheduler started:true
[INFO] 30 Jul 09:14:58.720 AM TestScheduler_Worker-1 [org.quartz.jobs.sample.HelloJob2]
Hello World! - Mon Jul 30 09:14:58 EDT 2012
[INFO] 30 Jul 09:14:58.721 AM TestScheduler_Worker-2 [org.quartz.jobs.sample.HelloJob2]
Hello World! - Mon Jul 30 09:14:58 EDT 2012
[INFO] 30 Jul 09:14:59.002 AM TestScheduler_Worker-3 [org.quartz.jobs.sample.HelloJob2]
Hello World! - Mon Jul 30 09:14:59 EDT 2012
[INFO] 30 Jul 09:15:00.003 AM TestScheduler_Worker-1 [org.quartz.jobs.sample.HelloJob]
Hello World! - Mon Jul 30 09:15:00 EDT 2012
[INFO] 30 Jul 09:15:00.003 AM TestScheduler_Worker-2 [org.quartz.jobs.sample.HelloJob2]
Hello World! - Mon Jul 30 09:15:00 EDT 2012
[INFO] 30 Jul 09:15:01.001 AM TestScheduler_Worker-3 [org.quartz.jobs.sample.HelloJob2]
Hello World! - Mon Jul 30 09:15:01 EDT 2012
[INFO] 30 Jul 09:15:02.001 AM TestScheduler_Worker-1 [org.quartz.jobs.sample.HelloJob2]
Hello World! - Mon Jul 30 09:15:02 EDT 2012
[INFO] 30 Jul 09:15:03.002 AM TestScheduler_Worker-2 [org.quartz.jobs.sample.HelloJob2]
Hello World! - Mon Jul 30 09:15:03 EDT 2012
[INFO] 30 Jul 09:15:04.002 AM TestScheduler_Worker-3 [org.quartz.jobs.sample.HelloJob]
Hello World! - Mon Jul 30 09:15:04 EDT 2012
[INFO] 30 Jul 09:15:04.003 AM TestScheduler_Worker-1 [org.quartz.jobs.sample.HelloJob2]
Hello World! - Mon Jul 30 09:15:04 EDT 2012
[INFO] 30 Jul 09:15:05.002 AM TestScheduler_Worker-2 [org.quartz.jobs.sample.HelloJob2]
Hello World! - Mon Jul 30 09:15:05 EDT 2012
[INFO] 30 Jul 09:15:06.001 AM TestScheduler_Worker-3 [org.quartz.jobs.sample.HelloJob2]
Hello World! - Mon Jul 30 09:15:06 EDT 2012
[INFO] 30 Jul 09:15:07.002 AM TestScheduler_Worker-1 [org.quartz.jobs.sample.HelloJob2]
Hello World! - Mon Jul 30 09:15:07 EDT 2012
[INFO] 30 Jul 09:15:08.002 AM TestScheduler_Worker-2 [org.quartz.jobs.sample.HelloJob]
Hello World! - Mon Jul 30 09:15:08 EDT 2012
[INFO] 30 Jul 09:15:08.003 AM TestScheduler_Worker-3 [org.quartz.jobs.sample.HelloJob2]
Hello World! - Mon Jul 30 09:15:08 EDT 2012
Can you please provide us with a sample project that can reproduce your issue ?
PS : this question is also posted on StackOverflow : http://stackoverflow.com/questions/11714410/quartz-with-couple-of-jobs-but-only-one-running