Jira usage very slow and cpu-usage very high, after a couple of days

Knut_Luebke

Hi there,

if this problem occures, we try to restart the jira-service first. But its never successful. The jira-service goes into the state "stopping service" but it could/will not be stopped within ~20-30min (very long time).

It`s necessary to terminate the corresponding tomcat-process manual.

Afterwards the jira-service is stoppend and the cpu-usage is in the normal range again ~10%. 

The problem repeats again after a couple of days.

 

We are running jira v8.2.4 under WindowsServer2012 R2 with an oracle database 12.1.0.2.0.

Our jira-instance is only accessible from our intranet. The instance is not reachable from the internet.

We created a thread dump from the last occurrence.

 

https://www.dropbox.com/s/bw1glftxe1pcwha/jira_threaddump.txt?dl=0

 

Can anybody help us what might cause this problem?

Thanks in advance for any help.

 

Regards 

-Knut

 

Andy Heinzer

Hi Knut,

I understand that your Jira instance appears to be getting into an unresponsive state after a few days and you are looking for more information about why.  Thanks for including the thread dump.  I used the samurai.jar utility to take a closer look at this thread dump.  I found that there were at least 2 threads blocked, and another 2 that were actively blocking.

Having blocked threads in that file are a clear indicator of a performance problem here, but by themselves they typically are not the source of the problem.  For that, we typically need to look at the blocking threads instead, which is where samurai is helpful.  The two threads that appear to be causing this blocking were titled:

Structure-Jobs4cb20abe System-Thread#2
JIRA-INFORM-Thread-0

The first thread is clearly related to the Structure plugin.  It might help to try to reach out to the Structure support team for help with troubleshooting that plugin to Jira.   I would try to focus on that thread first.

The second thread appears to be related to the Jira's native event listeners.  These can be used for triggering notifications on changes, or possibly utilized by third party plugin in Jira for triggering some other actions to happen.

I suspect that structure is trying to perform some huge amount of work and getting really bogged down the in the process, but it's unclear to as to the details of how or why. 

I hope this helps,

Andy