Symptom
- A server process fails to start due to a JVM crash.
- The logs in the work folder show errors similar to the following:
dev_server
================
F ********************************************************************************
F *** ERROR => Java VM crashed.
F ***
F *** Please see section 'Java process issues'
F *** in SAP Note 1316652 for additional information and trouble shooting advice.
F ********************************************************************************
std_server
================
# A fatal error has been detected by the SAP Java Virtual Machine:
#
# SIGSEGV (0xb) at pc=0x0a000200031daafc, pid=26607664, tid=11823
# accessing faulting address: 0x0a0002001fff0000
#
# JRE version: Java(TM) SE Runtime Environment (6.0_115-b12) (build 6.1.090)
# Java VM: SAP Java Server VM (6.1.090 25.51-b02 Apr 29 2016 16:37:17 - 61_REL - optU - aix ppc64 - 6 - bas2:268520 (mixed mode) compressed oops)
# Problematic frame:
# J4 27930 C2 com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.handleStartElement(Lcom/sun/org/apache/xerces/internal/xni/QName;Lcom/sun/org/apache/xerces/internal/xni/XMLAttributes;Lcom/sun/org/apache/xerces/internal/xni/Augmentations;)Z (506 bytes) @ 0x0a000200031daafc [0x0a000200031d9c80+0x0000000000000e7c] (sp=0x0000000121584c90) (pc=0x0a000200031daafc)
- The system runs on AIX OS.
- The heap size was recently increased to a larger size.
- JVM version used is 6.1 with patch lower than 101.
Read more...
Environment
SAP NetWeaver Application Server for Java
Product
Keywords
java virtual machine startup start starting bootstrap crashed vm jvm sigsegv xerces ppc64 heap size , 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.