Recurrent Crach of JIRA

Question

My JIRA crach every day whith following errors :

A fatal error has been detected by the Java Runtime Environment:
#
# SIGBUS (0x7) at pc=0x00007f31700523e9, pid=2147, tid=0x00007f30deecc700
#
# JRE version: OpenJDK Runtime Environment (8.0_202-b08) (build 1.8.0_202-b08)
# Java VM: OpenJDK 64-Bit Server VM (25.202-b08 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# V [libjvm.so+0x4313e9][thread 139848974034688 also had an error]
PerfClassTraceTime::initialize()+0x29
#
# 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:
# /tmp/hs_err_pid2147.log
[thread 139845375354624 also had an error]
[thread 139848506259200 also had an error]
[thread 139845017716480 also had an error]
[thread 139844723615488 also had an error]
[thread 139844724668160 also had an error]
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp

Do you have any idea where this might come from  ?

Nic Brough -Adaptavist- · Answer

Ok, nothing worrying there.  I'm afraid you'll need to be looking at the core dumps

Qabil · Answer

Thank a lot for your Quick answer :

this is my JVM settings:

Version de Java 1.8.0_202
Fournisseur de Java AdoptOpenJdk
Version de JVM 1.8
Fournisseur de JVM Oracle Corporation
Version d'implémentation de JVM 25.202-b08
Version d'exécution Java OpenJDK Runtime Environment
Java VM OpenJDK 64-Bit Server VM

-Djava.util.logging.config.file=/opt/atlassian/jira/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Xms768m -Xmx4608m
-XX:InitialCodeCacheSize=32m -XX:ReservedCodeCacheSize=512m -Djava.awt.headless=true -Datlassian.standalone=JIRA -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true
-Dmail.mime.decodeparameters=true -Dorg.dom4j.factory=com.atlassian.core.xml.InterningDocumentFactory
-Datlassian.plugins.startup.options= -Djdk.tls.ephemeralDHKeySize=2048 -Djava.protocol.handler.pkgs=org.apache.catalina.webresources
-Dorg.apache.catalina.security.SecurityListener.UMASK=0027 -Xloggc:/opt/atlassian/jira/logs/atlassian-jira-gc-%t.log -XX:+UseGCLogFileRotation
-XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=20M -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -XX:+PrintGCCause -XX:+ExplicitGCInvokesConcurrent
-Dignore.endorsed.dirs= -Dcatalina.base=/opt/atlassian/jira -Dcatalina.home=/opt/atlassian/jira -Djava.io.tmpdir=/opt/atlassian/jira/temp

Nic Brough -Adaptavist- · Answer

I am afraid there is no way to tell.  You need to analyse the core dump to see what the threads were all doing.  But they're currently disabled, so you don't have one to work through.

There might be something useful in the hs_err_pid log file it has written that might actually say "don't look in the core dump, look elsewhere", but it's a long-shot.

I would also want to check your JVM settings are valid - next time you run Jira, go to the system information page and look for the JVM settings section, it should have a pile of text with things like -Xmx1024m in it - those should be checked to make sure they're good for the Java that is running Jira.