JIRA Deadlocks when Running Tomcat 6.0.24
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
Symptoms
When running JIRA on Tomcat 6.0.24, there are periodic deadlocks. Thread dumps taken when JIRA is unresponsive show deadlocks like:
Found one Java-level deadlock:
=============================
"http-8080-6":
waiting to lock monitor 0x039664f4 (object 0x12aa4008, a org.apache.catalina.loader.WebappClassLoader),
which is held by "http-8080-5"
"http-8080-5":
waiting to lock monitor 0x0396655c (object 0x2a2005a8, a java.lang.String),
which is held by "http-8080-6"
Cause
There is a known bug in version 6.0.24 of tomcat that causes deadlocks in applications that use their own classloaders (such as JIRA). See Apache's bug tracker for more information.
Resolution
Upgrade to version 6.0.26 or higher of Tomcat and reinstall the JIRA ear-war, or install JIRA's latest stand-alone distribution.
Was this helpful?