I have a service implementation that uses Quartz.Net for several years now. All works fine and i allways tried to stay up to date with all external libraries, also with Quartz.Net.
I had some issues with version 3.1.x (unneccessary ms package installations) so i waited to version 3.2.x to upgrade.
I installed my services on several customer servers a week ago and a problem showed up that is quite unexplainable for me.
On customer servers that use for example windows server 2019 all my quarz jobs are fireing and working without problems. But I installed the same code package on a windows Server 2008 R2 of a customer and I realized that no jobs were started.
I looked into the log and there have been the normal initialization entries:
...
Scheduler meta-data: Quartz Scheduler (v3.2.3.0) 'QuartzSchedulerFactory' with instanceId 'NON_CLUSTERED'
Scheduler class: 'Quartz.Core.QuartzScheduler' - running locally.
NOT STARTED.
Currently in standby mode.
Number of jobs executed: 0
Using thread pool 'Quartz.Simpl.DefaultThreadPool' - with 10 threads.
Using job-store 'Quartz.Simpl.RAMJobStore' - which does not support persistence. and is not clustered.
...
QuartzScheduler ThreadID=1: Scheduler QuartzSchedulerFactory_$_NON_CLUSTERED started.
...
QuartzSchedulerThread ThreadID=6: Batch acquisition of 1 triggers
QuartzSchedulerThread ThreadID=6: Batch acquisition of 1 triggers
QuartzSchedulerThread ThreadID=6: Batch acquisition of 1 triggers
QuartzSchedulerThread ThreadID=6: Batch acquisition of 1 triggers
...
On all other installations i also have log entries like for example:
JobRunShell ThreadID=12: Calling Execute on job DEFAULT.JobQueueAwsJobDetail
But on the Vindows 2008 Server R2 those log entries are missing and no jobs are executed.
I tried to downgrade back to V3.0.7and now my service also runs the jobs on the old server and all works perfectly again...
Is there something I can do about that problem or am i stuck to the old version of Quartz.Net?
I have a service implementation that uses Quartz.Net for several years now. All works fine and i allways tried to stay up to date with all external libraries, also with Quartz.Net.
I had some issues with version 3.1.x (unneccessary ms package installations) so i waited to version 3.2.x to upgrade.
I installed my services on several customer servers a week ago and a problem showed up that is quite unexplainable for me.
On customer servers that use for example windows server 2019 all my quarz jobs are fireing and working without problems. But I installed the same code package on a windows Server 2008 R2 of a customer and I realized that no jobs were started.
I looked into the log and there have been the normal initialization entries:
...
Scheduler meta-data: Quartz Scheduler (v3.2.3.0) 'QuartzSchedulerFactory' with instanceId 'NON_CLUSTERED'
Scheduler class: 'Quartz.Core.QuartzScheduler' - running locally.
NOT STARTED.
Currently in standby mode.
Number of jobs executed: 0
Using thread pool 'Quartz.Simpl.DefaultThreadPool' - with 10 threads.
Using job-store 'Quartz.Simpl.RAMJobStore' - which does not support persistence. and is not clustered.
...
QuartzScheduler ThreadID=1: Scheduler QuartzSchedulerFactory_$_NON_CLUSTERED started.
...
QuartzSchedulerThread ThreadID=6: Batch acquisition of 1 triggers
QuartzSchedulerThread ThreadID=6: Batch acquisition of 1 triggers
QuartzSchedulerThread ThreadID=6: Batch acquisition of 1 triggers
QuartzSchedulerThread ThreadID=6: Batch acquisition of 1 triggers
...
On all other installations i also have log entries like for example:
JobRunShell ThreadID=12: Calling Execute on job DEFAULT.JobQueueAwsJobDetail
But on the Vindows 2008 Server R2 those log entries are missing and no jobs are executed.
I tried to downgrade back to V3.0.7and now my service also runs the jobs on the old server and all works perfectly again...
Is there something I can do about that problem or am i stuck to the old version of Quartz.Net?