Jira process becomes unresponsive without any type of excessive resource consumption in FIPS 140 enabled environment
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 becomes unresponsive at random intervals without an obvious cause. This behavior does not seem to directly correlate with any increase in usage or demand but instead appears to happen on a random basis.
Environment
FIPS 140 is enabled.
Diagnosis
Log entries simply stop, similar to the situation described in the KB article on the Out of Memory Killer, except that the process remains running instead of being terminated.
There is no substantial increase in load before this happens on CPU, memory, or database activity
Often plenty of memory and heap space will be unused and available when this issue surfaces
The stalled Jira process is using very close to 0% CPU once this happens, and the UI can no longer be accessed.
Jira's ports are still open with Tomcat listening for activity, but no pages are ever served
Thread dumps show stuck threads waiting for SSL/PKCS activity of multiple kinds:
Database access
General network communication
Every thread dealing with SSL in one way or another is stuck
The issue does not happen in other environments with different physical hardware that are otherwise identical
FIPS-140 compliance was turned on just before this issue began to appear
Cause
You have FIPS-140 enabled in your environment but your server's physical hardware does not support FIPS-140. Because of this, not all SSL connections are being negotiated properly and sometimes getting vital processes "stuck" within Jira.
Solution
Disable FIPS-140 compliance in your environment until the hardware has been upgraded to be compliant.
Was this helpful?