Symptom
The SAP application server JAVA crashes and the below error is logged in the trace files (dev_server<x>, std_server<x>) :
# A fatal error has been detected by the SAP Java Virtual Machine:
#
# SIGSEGV (0xb) at pc=0xffffffff7ddab3ac, pid=7599, tid=61106
# accessing faulting address: 0x0000000000000000
#
# JRE version: Java(TM) 2 Runtime Environment, Standard Edition (1.4.2_34) (build 4.1.046)
# Java VM: SAP Java Server VM (4.1.046 24.55-b03 Oct 1 2014 02:35:34 - 41_REL - optU - solaris sparc - 6 - bas2:226450 (mixed mode) compressed oops)
# Problematic frame:
# C [libc.so.1+0xab3ac] _ndoprnt+0x1e8 (sp=0xfffffffcf57f2240) (pc=0xffffffff7ddab3ac)
#
# Will write core dump when quitting, default location: /opt/sap/PCI/J04/j2ee/cluster/server0/core or core.7599
#
# An error report file with more information is saved as:
# /opt/sap/PCI/J04/j2ee/cluster/server0/hs_err_pid7599.log
#
# If you would like to submit a bug report, please visit:
# http://service.sap.com/message
# 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
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
Read more...
Environment
- SAP J2EE Engine 6.40
- SAP Netweaver AS Java 7.0x
- SAP Solution Manager 7.0
- SAP Process Integration - PI 7.0
Product
Keywords
SAP JVM 4.1.046, JVM 4.1.46, JVM Crash , KBA , BC-JVM , SAP Java Virtual Machine , BC-JAS-SF , Startup Framework , Bug Filed
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.