Jboss crash with core dump in libartemis-native-64.so+0x28c7
Article ID: 265804
Updated On:
Products
Issue/Introduction
The system caused Jboss crash with a java core dump. The other nodes are functioning properly, so there is no outage as such.
We are seeing the following error in the system logs.
-------------------
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f0512a3a8c7, pid=1140750, tid=0x00007f04cf59b700
#
# JRE version: Java(TM) SE Runtime Environment (8.0_281-b09) (build 1.8.0_281-b09)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.281-b09 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libartemis-native-64.so+0x28c7] Java_org_apache_activemq_artemis_nativo_jlibaio_LibaioContext_blockedPoll+0x67
#
# 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/CA/jboss/jboss-eap-7.2.9/bin/hs_err_pid1140750.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
#
./standalone.sh: line 358: 1140750 Aborted (core dumped) "/opt/CA/Java/jdk1.8.0_281/bin/java" -D"[Standalone]" -server -Djboss.modules.system.pkgs=com.wily,com.wily.*,org.jboss.byteman -Xbootclasspath/p:/opt/wily/Agent.jar -javaagent:/opt/wily/Agent.jar -DagentProfile=/opt/wily/core/config/IntroscopeAgent.profile -Xms16G -Xmx16G -XX:+UseG1GC -XX:+UseStringDeduplication -XX:+UseCompressedOops -Djava.net.preferIPv4Stack=true -Djava.security.egd=file:/dev/./urandom -Dcom.sun.jersey.server.impl.cdi.lookupExtensionInBeanManager=true -Dlog4j.configurationFile=/com/netegrity/config/log4j_jboss.xml "-Dorg.jboss.boot.log.file=/opt/CA/jboss/jboss-eap-7.2.9/standalone/log/server.log" "-Dlogging.configuration=file:/opt/CA/jboss/jboss-eap-7.2.9/standalone/configuration/logging.properties" -jar "/opt/CA/jboss/jboss-eap-7.2.9/jboss-modules.jar" -mp "/opt/CA/jboss/jboss-eap-7.2.9/modules" org.jboss.as.standalone -Djboss.home.dir="/opt/CA/jboss/jboss-eap-7.2.9" -Djboss.server.base.dir="/opt/CA/jboss/jboss-eap-7.2.9/standalone" -c standalone-full-ha.xml -b 0.0.0.0 -Djgroups.tcpping.initial_hosts=##.##.###.#[7601],##.##.###.##[7601],##.##.###.## -Djboss.node.name=iamnodep104 -Djgroups.bind_addr=##.##.###.## -Dnete.j2ee.vendor=jboss -Djboss.as.management.blocking.timeout=3600
Environment
Release : 14.x
Cause
The JVM has crashed in the following code.
org.apache.activemq.artemis.nativo.jlibaio
A similar, though not necessarily identical, crash has been reported by RedHat. If you have a RedHat account login and see the following:
https://access.redhat.com/solutions/5080901
JVM crash in org.apache.activemq.artemis.nativo.jlibaio.LibaioContext.done() method
Environment
- Red Hat AMQ 7.2.6
- Async I/O journal persistence
- Red Hat Enterprise Linux (RHEL) 7
- kernel 3.10.0-1127.8.2.el7.x86_64
- kernel 3.10.0-1136.el7.x86_64
Issue
- All JBoss servers in the domain are crashing with the fatal error log showing the following stack:
j org.apache.activemq.artemis.nativo.jlibaio.LibaioContext.done(Lorg/apache/activemq/artemis/nativo/jlibaio/SubmitInfo;)V+1
v ~StubRoutines::call_stub
V [libjvm.so+0x685d2b] JavaCalls::call_helper(JavaValue*, methodHandle*, JavaCallArguments*, Thread*)+0xddb
V [libjvm.so+0x6cd5c8] jni_invoke_nonstatic(JNIEnv_*, JavaValue*, _jobject*, JNICallType, _jmethodID*, JNI_ArgumentPusher*, Thread*) [clone .constprop.109]+0x208
V [libjvm.so+0x6cf6a6] jni_CallVoidMethod+0x166
C [libartemis-native-64.so+0x29b6] Java_org_apache_activemq_artemis_nativo_jlibaio_LibaioContext_blockedPoll+0x156Resolution
Contact your RedHat JBoss support for diagnosis and resolution.
Feedback
