When changing the min/max counts for the Scheduled Jobs pooling subsystem, this does not change the number of Quartz job threads running.
pool :jobs do
8.times do |x|
job MyJob do
cron '* * * * * ?'
Give the above configuration, I would expect that there would be at least 8 concurrently executing jobs. Only 3 ever execute concurrently. This appears to be because org.quartz.simpl.SimpleThreadPool=3. And this does not change.
This in effect negates the usefulness of being able to set the min/max pools size for the jobs subsystem. From the logs we can see that the number of threads available for Quartz jobs is set to 3.
14:36:23,509 INFO [org.quartz.core.QuartzScheduler] (MSC service thread 1-12) Scheduler meta-data: Quartz Scheduler (v1.8.5) 'JobScheduler$2012-07-06_torquebox-knob.yml' with instanceId 'stiletto.local1341693383488'
Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
Currently in standby mode.
Number of jobs executed: 0
Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 3 threads.
Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered.