Issue is related to upgraded Spring boot from 1.3.8 => 2.1.7. In Spring boot 2.x was fixed ignoring 'org.quartz.scheduler.instanceName' property from quartz.properties file:
https://github.com/spring-projects/spring-boot/issues/14243
Which we have configured in each profile to 'idm-scheduler-instance'. But in quartz database was filled spring bean name 'schedulerFactoryBean' as instance name. Quartz property starts to be effective after Spring was upgraded => previously scheduled tasks are present in database, but ignored (no scheduler instance 'schedulerFactoryBean' exists now).
We decided to change quartz.properties 'org.quartz.scheduler.instanceName=schedulerFactoryBean' => we don't want to close a door for using more scheduler instancies in future (we could fix it directly in code as other option ~ configured instance name will be still ignored, but configuration will be not effective anymore).
Solution:
For project, where CzechIdM version 10.x is already installed and task were rescheduled, don't change anything now => tasks will be scheduled under 'idm-scheduler-instance'.
For project, where CzechIdM version 10.x will be upgraded from any older version, change property 'org.quartz.scheduler.instanceName=schedulerFactoryBean' in your project profiles => tasks will be scheduled under 'schedulerFactoryBean', previously scheduled task will be preserved.
For projects with new CzechIdM version 10 instalation, don't change anything => tasks will be scheduled under 'idm-scheduler-instance' by default.
Warning:
Be aware to change 'org.quartz.scheduler.instanceName' value in you quartz.properties file, if you don't want to use different or clustered scheduler => tasks need to be rescheduled after any change.
Doc:
https://github.com/bcvsolutions/CzechIdMng/blob/develop/MIGRATION.md#changed-properties
Could you provide me a feedback, please?
