SAP Knowledge Base Article - Preview

2167686 - SAP JVM crashes with "SIGILL (0x4)" Signal


While running the SAP JVM it suddenly crashes. In the logs like hs_err_pidXXXXX.log (SAP Note 1500116) you have an exception similar to:

# A fatal error has been detected by the SAP Java Virtual Machine:
#  SIGILL (0x4) at pc=0x0004a55c00007a55, pid=28959, tid=140656537736960
# address of faulting instruction: 0x0004a55c00007a55
# JRE version: Java(TM) SE Runtime Environment (6.0_71-b11) (build 6.1.061)
# Java VM: SAP Java Server VM (6.1.061 24.51-b03 Jan 19 2014 01:00:29 - 61_REL - optU - linux amd64 - 6 - bas2:209888 (mixed mode) )
# Problematic frame:
# C  []  pthread_join+0x10b (sp=0x00007fff72cd8e40) (pc=0x000000364f80804b)
# No core dump will be written (Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again)
# If you would like to submit a bug report, please visit:
# Please save the hs_err file(s) and the written core dump for further error analysis
# See SAP note 1500116 for further information on collecting core dumps after SAPJVM crashes





SAP Java Virtual Machine all versions


signal, 4, code, 0, kill, process, os , KBA , BC-JVM , SAP Java Virtual Machine , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.