Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.15.2
-
Fix Version/s: 3.17.0
-
Component/s: Logging, Scheduled Tasks
-
Labels:
-
Release Note:Yes
Description
Actual
If a trigger goes missing in the database then we end up spamming the logs in QuartzSchedulerSPI.java:730.
Expected
We should not spam the logs. In addition, when this exceptional behavior occurs an admin should be made aware of change as this will affect the frequency at which a task is run. Triggers should not be missing so placeholder triggers will be created with a manual run frequency by default.
Considerations
We could add a new system status check that reports if jobs are missing triggers/listeners or generically in error, then the error makes it to the user but does not build up GB of logs in a day. If we must leave the logging then recommend we consider the highest level instead of warn.
Attachments
Issue Links
- depends on
-
NEXUS-18983 If NXRM is read-only or lacks quorum, then run now triggers make startup fail.
-
- Closed
-
- relates
-
NEXUS-16912 WARN QuartzSchedulerSPI Job missing listener omitting from results
-
- Open
-
- testing discovered
-
NEXUS-19602 System Nodes View in UI incorrectly shows wrong state of read only mode button
-
- New
-