Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Fixed
Priority: Low
Fix Version/s: 3.9.6, 3.10.0
Affects Version/s: 3.2.7, 3.3.0, 3.7.0, 3.8.1, 3.9.3
Component/s: Automation, SLA
Labels:
- pse-request

Fixed in Long Term Support Release/s:

Download 3.9
Symptom Severity:
Severity 2 - Major
UIS:
92
Bug Fix Policy:
View Atlassian Server bug fix policy

Description

Problem definition

SLA does not stop reliably despite all conditions met.
Automations based on SLA events are not getting triggered at all.

Different exceptions can be found in the log in different cases, for example.

2017-10-06 04:48:25,011 ajp-nio-8009-exec-378 WARN admin 288x10990101x5 x26x7u 10.10.10.10,120.10.10.120 /secure/CommentAssignIssue.jspa [c.a.s.i.sla.threshold.SlaThresholdEventManagerImpl] SLA Threshold Events timed promise could not be scheduled for issue 'SDS-1234
java.lang.RuntimeException: l.

2017-10-06 04:36:08,255 ajp-nio-8009-exec-376 WARN agerak 276x10974985x1 18dmn9j 10.95.20.28,130.164.19.135 /secure/CommentAssignIssue.jspa [c.a.s.i.sla.threshold.SlaThresholdEventManagerImpl] SLA Threshold Events timed promise could not be scheduled for issue 'LORE-76084
java.lang.RuntimeException: Failed to retrieve Timed Promise history row after insertion.

Attachments

Issue Links

is related to

JSDSERVER-5059 SLA Update Lock to be issue level and not unlock until Timed Promise scheduled

Closed

JSDSERVER-5299 SLA custom field should use last updated value if the event of a race condition

Closed

is cloned by: JSMDC-1373 Loading...

relates to: JSMDC-1372 Loading...

Activity

People

Assignee:: moofoo (Inactive)

Reporter:: Michelle Chin

Votes:: 13 Vote for this issue

Watchers:: 15 Start watching this issue

Dates

Created:: 03/Nov/2017 11:45 AM

Updated:: 07/Dec/2023 3:23 PM

Resolved:: 25/Apr/2018 11:37 PM

SLA occasionally does not stop or SLA events-based automation does not get triggered reliably