Symptom
The SAP JVM is crashing with a hs_err file containg the following problematic frame:
#
# A fatal error has been detected by the SAP Java Virtual Machine:
#
# SIGFPE (0x8) at pc=0x1fffffffff6f0c42, pid=5251, tid=3165299
# address of faulting instruction: 0x1fffffffff6f0c42
#
# JRE version: 6.0_45-b05
# Java VM: SAP Java Server VM (6.1.049 23.5-b02 Apr 19 2013 04:21:48 - 61_REL - optU - hpux ia64 - 6 - bas2:194331 (mixed mode) compressed oops)
# Problematic frame:
# V [libjvm.so+0x2a88c42] ProfilingHeartBeatHook::info_taken(HeartBeatEvent*)+0x5a2 (sp=0x1fffffffaf601d20) (bsp=0x1fffffffaf5002f8) (pc=0x1fffffffff6f0c42)
#
#
Read more...
Environment
- Release Independent
- SAP NetWeaver
Product
Keywords
SAP JVM 4.1 5.1 6.1 7.1, hs_err, heartbeat, SmallHeartBeatInGcHistory, A fatal error has been detected by the SAP Java Virtual Machine, Problematic frame, ProfilingHeartBeatHook, info_takenHeartBeatEvent , 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.