2288732 - Problematic frame: get_exit_frame_monitor leads to SAPJVM crash

The SAP application server SAP JVM 6.1.68 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=0x00000000007336ae, pid=15269, tid=988
# accessing faulting address: 0x0000000000000002
#
# JRE version: Java(TM) SE Runtime Environment (6.0_75-b13) (build 6.1.068)
# Java VM: SAP Java Server VM (6.1.068 24.55-b03 Jun 22 2014 00:45:31 - 61_REL - optU - solaris amd64 - 6 - bas2:220276 (mixed mode) compressed oops)
# Problematic frame:
# C  [jstart+0x3336ae]  _get_exit_frame_monitor+0x3336ae (sp=0xfffffd7e381fb580) (pc=0x00000000007336ae)
#
# Will write core dump when quitting, default location: /usr/sap/ERS/J11/j2ee/cluster/server4/core or core.15269
#
# 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.
#

• SAP Netweaver AS Java 7.3x
• SAP Netweaver AS Java 7.40
• SAP Process Integration - PI 7.30
• SAP Process Orchestration 7.31
• SAP Process Orchestration 7.4*
• SAP SOLUTION MANAGER 7.2

JVM 6.1.68, get_exit_frame_monitor, SAP JVM 6.1, JVM 6.1, Problematic frame, Java AS fails, JVM bug , KBA , BC-JVM , SAP Java Virtual Machine , Bug Filed