A fatal error has been detected by the Java Runtime Environment
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
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
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.jspDiagnosis
Environment
- 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
Last modified on Mar 30, 2016
Powered by Confluence and Scroll Viewport.