JIRA not responsive, high cpu load. Threaddump attached

[P]

Hello,

we're running quite an old JIRA instance and since today we cannot really work with JIRA (and the server its running on) as it procudes quite a high cpu load (~80%)

The JIRA issues itself are non responsive and will not load until a couple of minutes (even than, its simple gambling if its working or not)

I attached a threaddump after I restarted JIRA.

Before this attempt to restart JIRA we were able to access it for an hour or two until it got really slow again.

Some setup information:

JIRA v6.0.1#6096-sha1:e4a48bd

on:

Ubuntu 12.04

12GB RAM (DDR2)

CPU (???)

Non VM enviroment.

Thanks for any help.

//Edit 2015-05-12

cpuinfo:

cpuinfo:
```
root@server01:/home/p.querner# cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 15
model           : 4
model name      : Intel(R) Xeon(TM) CPU 3.00GHz
stepping        : 3
cpu MHz         : 2999.841
cache size      : 2048 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 1
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 5
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc pebs bts pni dtes64 monitor ds_cpl cid cx16 xtpr
bogomips        : 5999.68
clflush size    : 64
cache_alignment : 128
address sizes   : 36 bits physical, 48 bits virtual
power management:
processor       : 1
vendor_id       : GenuineIntel
cpu family      : 15
model           : 4
model name      : Intel(R) Xeon(TM) CPU 3.00GHz
stepping        : 3
cpu MHz         : 2999.841
cache size      : 2048 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 1
apicid          : 1
initial apicid  : 1
fpu             : yes
fpu_exception   : yes
cpuid level     : 5
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc pebs bts pni dtes64 monitor ds_cpl cid cx16 xtpr
bogomips        : 6000.24
clflush size    : 64
cache_alignment : 128
address sizes   : 36 bits physical, 48 bits virtual
power management:
```

JVM Info: (setenv.sh in my JIRA /bin dir)

# JVM_SUPPORT_RECOMMENDED_ARGS=""
JVM_SUPPORT_RECOMMENDED_ARGS="-Datlassian.plugins.enable.wait=300"
#
# The following 2 settings control the minimum and maximum given to the JIRA Java virtual machine.  In larger JIRA instances, the maximum amount will need to be increased.
#
JVM_MINIMUM_MEMORY="256m"
JVM_MAXIMUM_MEMORY="768m"
#
# The following are the required arguments for JIRA.
#
JVM_REQUIRED_ARGS="-Djava.awt.headless=true -Datlassian.standalone=JIRA -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Dmail.mime.decodeparameters=true"

20150511.jira-atlassian.threaddump.log

[P]

I have added information about JVM and cput @Randall Fisher mario günter

[David Di Blasio]

Hi Pascal,
If you're currently in maintenance you can open up a support ticket at https://support.atlassian.com, and one of our engineers can look into this if you like. 

Cheers

[Mario Günter]

execute in bash to find out CPU information:

$ cat /proc/cpuinfo

[Randall Fisher]

You gave stats for the system, can you give stats for how you have sized the JVM.