JIRA Not able to open one issue
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Jira was not opening one particular issue VLBxx-xxx6 every time. It was showing a blank screen for that issue. All other issues were working fine.
Environment
Jira Server or DC
Diagnosis
The following stuck thread detection Warning was seen in the Tomcat Catalina logs.
The below warning shows that multiple HTTP threads http-nio-8080-exec-1xxx are stuck in serving request https://<jira_url>/jira/browse/VLBxx-xxx6 for more than 120 seconds.
1
2
3
4
5
ubuntu@instenv-287013-xean:/Attachments/Jira_support_2024-05-03-15-32-20_2024-05-03T14:02:01.911Z$ grep -i "/VLBxx-xxx6" -R . *
./tomcat-logs/catalina.2024-04-30.log:30-Apr-2024 14:34:41.070 WARNING [Catalina-utility-2] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadDetected Thread [http-nio-8080-exec-1xxx] (id=[38xxx50]) has been active for [127,711] milliseconds (since [4/30/24 2:32 PM]) to serve the same request for [https://<jira_url>/jira/browse/VLBxx-xxx6] and may be stuck (configured threshold for this StuckThreadDetectionValve is [120] seconds). There is/are [61] thread(s) in total that are monitored by this Valve and may be stuck.
./tomcat-logs/catalina.2024-04-30.log:30-Apr-2024 14:35:11.131 WARNING [Catalina-utility-1] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadDetected Thread [http-nio-8080-exec-1xxx] (id=[38xxx40]) has been active for [124,594] milliseconds (since [4/30/24 2:33 PM]) to serve the same request for [https://<jira_url>/jira/browse/VLBxx-xxx6] and may be stuck (configured threshold for this StuckThreadDetectionValve is [120] seconds). There is/are [62] thread(s) in total that are monitored by this Valve and may be stuck.
./tomcat-logs/catalina.2024-05-02.log:02-May-2024 11:31:08.910 WARNING [Catalina-utility-2] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadDetected Thread [http-nio-8080-exec-1xxx] (id=[37xxx00]) has been active for [128,931] milliseconds (since [5/2/24 11:28 AM]) to serve the same request for [https://<jira_url>/jira/rest/api/latest/issue/VLBxx-xxx6/remotelink?xoauth_requestor_id=kakula] and may be stuck (configured threshold for this StuckThreadDetectionValve is [120] seconds). There is/are [64] thread(s) in total that are monitored by this Valve and may be stuck.
./tomcat-logs/catalina.2024-05-02.log:02-May-2024 12:01:32.387 WARNING [Catalina-utility-2] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadDetected Thread [http-nio-8080-exec-1xxx] (id=[37xxx81]) has been active for [128,454] milliseconds (since [5/2/24 11:59 AM]) to serve the same request for [https://<jira_url>/jira/browse/VLBxx-xxx6] and may be stuck (configured threshold for this StuckThreadDetectionValve is [120] seconds). There is/are [65] thread(s) in total that are monitored by this Valve and may be stuck.Further analyzing the Tomcat Catalina logs, warnings for stuck thread detections show the stack trace, showing that while serving the request https://<jira_url>/jira/browse/VLBxx-xxx6, Jira was trying to execute the code from com.herzum.jira.plugin.approval.
1
29-Apr-2024 07:35:41.635 WARNING [Catalina-utility-1] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadDetected Thread [http-nio-8080-exec-1xxx] (id=[38xxx26]) has been active for [120,110] milliseconds (since [4/29/24 7:33 AM]) to serve the same request for [https://<jira_url>/jira/browse/VLBxx-xxx6] and may be stuck (configured threshold for this StuckThreadDetectionValve is [120] seconds). There is/are [59] thread(s) in total that are monitored by this Valve and may be stuck. java.lang.Throwable at java.base@11.0.19/java.lang.Object.wait(Native Method) at com.herzum.jira.plugin.approval.manager.impl.ApprovalIssueManagerImpl.lock(ApprovalIssueManagerImpl.java:293) at com.herzum.jira.plugin.approval.manager.impl.ApprovalIssueManagerImpl.reindexSingleIssueSynch(ApprovalIssueManagerImpl.java:267) at com.herzum.jira.plugin.approval.manager.impl.ApprovalIssueManagerImpl.reindexSingleIssue(ApprovalIssueManagerImpl.java:242) at com.herzum.jira.plugin.approval.manager.impl.DataTransferManagerImpl.getApprovalMapParams(DataTransferManagerImpl.java:826) at com.herzum.jira.plugin.approval.manager.impl.DataTransferManagerImpl.getApprovalMapParams(DataTransferManagerImpl.java:794) at com.herzum.jira.plugin.approval.view.ApprovalWebPanel.getContextMap(ApprovalWebPanel.java:26) at com.atlassian.jira.plugin.webfragment.contextproviders.AbstractJiraContextProvider.getContextMap(AbstractJiraContextProvider.java:28) at com.atlassian.plugin.web.descriptors.DefaultWebPanelModuleDescriptor$ContextAwareWebPanel.getHtml(DefaultWebPanelModuleDescriptor.java:127) at com.atlassian.jira.web.component.ModuleWebComponentImpl.renderModule(ModuleWebComponentImpl.java:83) at com.atlassian.jira.web.component.ModuleWebComponentImpl.lambda$renderModuleAndLetNoThrowablesEscape$0(ModuleWebComponentImpl.java:70) at com.atlassian.jira.web.component.ModuleWebComponentImpl$$Lambda$5081/0x0000000804860c40.run(Unknown Source) at com.atlassian.ozymandias.SafePluginPointAccess.runnable(SafePluginPointAccess.java:404) at com.atlassian.jira.web.component.ModuleWebComponentImpl.renderModuleAndLetNoThrowablesEscape(ModuleWebComponentImpl.java:68) at com.atlassian.jira.web.component.ModuleWebComponentImpl.renderModule(ModuleWebComponentImpl.java:58) at jdk.internal.reflect.GeneratedMethodAccessor1003.invoke(Unknown Source) Cause
Herzum Approval Plugin was enabled on the customer Jira instance. Due to unknown reason http threads was getting stuck while executing code from com.herzum.jira.plugin.approval in process of serving the request to open issue VLBxx-xxx6
Solution
Disable the Herzum Approval Plugin and try accessing the issue again.
If issue is resolved then contact the plugin vendor with stack trace to further investigate the reason for threads getting stuck/ issue not accessible.
Was this helpful?