A fatal error has been detected by the Java Runtime 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
Problem
Jira unable to start up due to this error :
The following appears in the XXXXXXXXXXX.log
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
INFORMATION: Starting Servlet Engine: Apache Tomcat/7.0.55
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f673a330b4b, pid=9925, tid=140081016010496
#
# JRE version: Java(TM) SE Runtime Environment (8.0_51-b16) (build 1.8.0_51-b16)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.51-b03 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# V [libjvm.so+0x7bab4b] Klass::external_name() const+0x1b
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /opt/atlassian/jira/bin/hs_err_pid9925.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jspEnvironment
VM host on the server
Jira is running on a debian virtual machine running with KVM on the VM host
Cause
Not enough memory is allocated to the VM Host.
Resolution
Increase the memory ( 8GB to 16GB ) to the machine and the restart all VMs.
Was this helpful?