JVM Segfault (SIGSEGV) After Plugin Initialisation
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
JIRA crashes on start up after the plugin initialisation has completed with a JVM segfault.
1
2
3
4
5
6
7
8
9
10
11
12
13
2009-08-28 12:03:16,541 main INFO [atlassian.plugin.manager.DefaultPluginManager\] Plugin system started in 0:00:18.757#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# SIGSEGV (0xb) at pc=0x00007f15fb2976b4, pid=5718, tid=139730367412560
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0_18-b02 mixed mode)
# Problematic frame:
# V [libjvm.so+0x5bc6b4]
#
# An error report file with more information is saved as hs_err_pid5718.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
Cause
This is a known bug in JVM versions 1.5.0_18-b02 and earlier. The bug is tracked by Sun.
Resolution
Upgrade Java JVM to version 1.5.0_20 or higher. See Java Crashes for further tips.
Was this helpful?