SchedulerAccessor needs to catch primary key violation on reschedule (due to Quartz race condition) [SPR-17114] #21651
Related to #6506. While "rescheduling" a Quartz job's trigger within cluster of applications that are starting, Quartz can throw a Primary Key Violation error while trying to add a trigger that some other node in the cluster already added. A catch-and-ignore was put into
The error causes the context to fail to load and thus the application fails to start. Can the
Stack trace attached in log file.
Reference URL: #6506
Backported to: 4.3.19
The text was updated successfully, but these errors were encountered: