-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Medium
-
Affects Version/s: 4.20.6, 4.20.14
-
Component/s: Automation
-
None
-
14
-
Severity 2 - Major
-
11
The customer encountered slowness in all Atlassian applications. After checking at the database end, they found that they were hit by a bug mentioned in JSDSERVER-5493. They followed the same steps mentioned in the workaround and it resolved the issue
Support is unable to reproduce the issue.
Workaround:
The following query can be used to check for rows that may encounter this behavior:
select Q."NAME", Q."MESSAGE_COUNT", count(M."ID") as real_message_count from "AO_319474_QUEUE" as Q left join "AO_319474_MESSAGE" as M on M."QUEUE_ID" = q."ID" group by Q."NAME", Q."MESSAGE_COUNT" having count(M."ID") = 0 AND Q."MESSAGE_COUNT" != 0;
If thread dumps reveal looping threads, use the following to correct the offending rows.
update "AO_319474_QUEUE" set "MESSAGE_COUNT" = 0 where "NAME" in (select Q."NAME" from "AO_319474_QUEUE" as Q left join "AO_319474_MESSAGE" as M on M."QUEUE_ID" = q."ID" group by Q."NAME", Q."MESSAGE_COUNT" having count(M."ID") = 0 AND Q."MESSAGE_COUNT" != 0);
- is a regression of
-
-
- Closed
-