After running the server app. for about 6 hours over the night, I saw that it had stopped at the following line in JobSchedulingManager.ScheduleJob:
Scheduler.ScheduleJob(jobDetail.Build(), trigger);
The exception details were:
An unhandled exception of type 'Quartz.ObjectAlreadyExistsException' occurred in Quartz.dll.
Additional information: Unable to store Job: 'ratingChangeGroup.ratingChangeJob4', because one already exists with this identification.
I'm not sure why it was trying to schedule the job again 6 or so hours later, but maybe it's the nature of the quartz threading?
After running the server app. for about 6 hours over the night, I saw that it had stopped at the following line in JobSchedulingManager.ScheduleJob:
Scheduler.ScheduleJob(jobDetail.Build(), trigger);The exception details were: An unhandled exception of type 'Quartz.ObjectAlreadyExistsException' occurred in Quartz.dll. Additional information: Unable to store Job: 'ratingChangeGroup.ratingChangeJob4', because one already exists with this identification.
I'm not sure why it was trying to schedule the job again 6 or so hours later, but maybe it's the nature of the quartz threading?