-
Bug
-
Resolution: Won't Fix
-
Low
-
None
-
Mindville - Pre Bundled
-
None
-
Severity 3 - Minor
-
Issue Summary
Jira unresponsive due to high amount of Insight content
Steps to Reproduce
Our customer updated single insight object with 1800 references in one field using import. This field was put in to list columns, as a result become Jira unresponsive in time of higher load, I can see stuck threads in /navlist, first ended in 8 minutes, the other hadn't ended at all.
Expected Results
Jira remains to function.
Actual Results
Jira unresponsive in time of higher load, I can see stuck threads in /navlist, first ended in 8 minutes, the other hadn't ended at all.:
16-Oct-2020 12:48:08.113 WARNING [ContainerBackgroundProcessor[StandardEngine[Catalina]]] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadDetected Thread [http-nio-8081-exec-38] (id=[423]) has been active for [127,709] milliseconds (since [10/16/20 12:46 PM]) to serve the same request for https://jirait.sk/jira/rest/insight/1.0/object/navlist and may be stuck (configured threshold for this StuckThreadDetectionValve is [120] seconds). There is/are [1] thread(s) in total that are monitored by this Valve and may be stuck. 16-Oct-2020 12:52:58.802 WARNING [ContainerBackgroundProcessor[StandardEngine[Catalina]]] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadDetected Thread [http-nio-8081-exec-66] (id=[452]) has been active for [129,445] milliseconds (since [10/16/20 12:50 PM]) to serve the same request for https://jirait.sk/jira/rest/insight/1.0/object/navlist and may be stuck (configured threshold for this StuckThreadDetectionValve is [120] seconds). There is/are [2] thread(s) in total that are monitored by this Valve and may be stuck. 16-Oct-2020 12:53:52.979 WARNING [ContainerBackgroundProcessor[StandardEngine[Catalina]]] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadCompleted Thread [http-nio-8081-exec-38] (id=[423]) was previously reported to be stuck but has completed. It was active for approximately [462,631] milliseconds. There is/are still [1] thread(s) that are monitored by this Valve and may be stuck.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
This is not to consider as a bug. Recommendation is to use many to one instead of one to many in this case.