-
Type: Bug
-
Status: Resolved
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 5.8
-
Fix Version/s: 5.8.0-HF17, 5.9.5
-
Component/s: Clustering
When the cluster mode is activated, the first startup properly registers the schedulers
INFO [SchedulerServiceImpl] Registering Schedule workflowInstancesCleanup (cron=0 59 23 * * ?) INFO [SchedulerServiceImpl] Registering Schedule escalationScheduler (cron=0 0/5 * * * ?) INFO [SchedulerServiceImpl] Registering Schedule workManagerCleanup (cron=0 0/5 * * * ?) INFO [SchedulerServiceImpl] Registering Schedule softDeleteCleanup (cron=0 0/15 * * * ?) INFO [SchedulerServiceImpl] scheduler started
but the next one only unregisters the previously registered schedulers
INFO [SchedulerServiceImpl] Unregistering schedule with idworkflowInstancesCleanup INFO [SchedulerServiceImpl] Unregistering schedule with idescalationScheduler INFO [SchedulerServiceImpl] Unregistering schedule with idworkManagerCleanup INFO [SchedulerServiceImpl] Unregistering schedule with idsoftDeleteCleanup INFO [SchedulerServiceImpl] scheduler started
- depends on
-
NXP-7303 proper behavior of Scheduler Service in clusters
- Resolved