TimeSheet plugin long response times crashed our Jira instance
Hello, Last evening, we had a severe issue with our Enterprise Jira instance which eventually led it to crash. After contacting the vendor, they pointed to the Time Sheet report and gadget plugin. We are currently running Jira 6.4.13 with JIRA Timesheet Reports and Gadgets Plugin version 2.9.7.7. The vendor recommended that we provided you a heap dump for you to take a look at. Please let me know where I can upload this in a private forum. If you need any additional information please let me know. Thanks!
Atlassian Premiere Support response to incident: {noformat} Looking into this we found that the majority of the threads were from a single source. There were over 140 of these same threads, there is a max of 150 threads in your current configuration. Request Details: Type|Name |Value
ref |userName|* ref |requestUrl|https://forge.lmig.com/issues/secure/ConfigureReport.jspa
Digging further into these threads it looks like the system is trying to create some kind of report: at com.fdu.jira.plugin.report.pivot.Pivot.generateReport(Lcom/atlassian/jira/web/action/ProjectActionSupport;Ljava/util/Map;Z)Ljava/lang/String; (Pivot.java:99) at com.fdu.jira.plugin.report.AbstractTimebaseReport.generateReportHtml(Lcom/atlassian/jira/web/action/ProjectActionSupport;Ljava/util/Map;)Ljava/lang/String; These classes look related to the Timesheet Reprots and Gadgets Plugin:
I'd also recommend providing the same heap dump data to the plugin vendor
Comments (5)
-
-
reporter The heap dump is almost 2 gb compressed. Can you provide me with a google drive upload space or something similar?
-
-
Hi Christopher,
Sorry, I can't figure out anything from the support files.
One idea though, please check email subscriptions in Administration - Add-ons - Timesheet Subscriptions and remove orphan or undesired subscriptions. I've seen few "User not found" errors from Timesheet Email Job in log. And the following statement: "over 140 of these same threads" from your analysis, makes me think that there might be too many email subscriptions.
From other hand, if JIRA crashed during report request, it might be not relevant.
Thank you.
-
- changed status to resolved
- Log in to comment
Hi Christopher,
Please use azhdanov at gmail.com, if possible.
Thank you.