-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
7.3.6
-
7.03
-
32
-
Severity 2 - Major
-
4
-
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Summary
In some cases JIRA CaesiumScheduler can create more then single record in clusteredjob table.
This will lead to problems similar to one in JRASERVER-64325: method getJobDetails expects single uniq value from DB, while clusteredjob table does not ensure this.
Steps to Reproduce
- TBD
Expected Results
Caesium ensures data integrity
Actual Results
CaesiumScheduler can create more then single record in clusteredjob table.
Notes
Problem is largely mitigated by implementing UNIQ index "clusteredjob_jobid_idx" (job_id) as part of JRASERVER-64325
Workaround
- causes
-
JRASERVER-64325 Jira fails to start due to duplicate job IDs in the clusteredjob table
- Closed
-
JRASERVER-66593 Duplicated "com.atlassian.jira.plugin.ext.bamboo.service.PlanStatusUpdateJob" job created during each JIRA restart
- Closed
- relates to
-
JRACLOUD-64326 JIRA CaesiumSchedulerService can insert duplicated records into clusteredjob
- Closed
-
RUM-2235 Loading...