SAP's NetWeaver product is built on JVM as a JNI C++ component.

SAP's "jlaunch.exe" process exits unexpectedly leaving hs_err_pid.log
file behind.

The problem is not reproducible, however happens on a daily basis.

Here is a snippet of hs_err_pid.log file. For details, please see
attachments section.

% more hs_err_pid3872.log
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# Internal Error (53484152454432554E54494D450E435050017C), pid=3872, tid=5648
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (1.4.2_13-b06 mixed mode)

--------------- T H R E A D ---------------

Current thread (0x0000000008db60b0): JavaThread "SAPEngine_Application_Thread[impl:3]_19" [_thread_in_Java, id=5648]

Stack: [0x000000000ec60000,0x000000000ee60000)

--------------- P R O C E S S ---------------

Java Threads: ( => current thread )
  0x000000000a7b0dd0 JavaThread "Java2D Disposer" daemon [_thread_blocked, id=4108]
[ ... ]
=>0x0000000008db60b0 JavaThread "SAPEngine_Application_Thread[impl:3]_19" [_thread_in_Java, id=5648]
[ ... ]


Error ID 53484152454432554E54494D450E435050017C = sharedRuntime.cpp, line 380

374 // (Note: This path would also be taken for divide-by-zero
375 // exceptions, if they could possibly arise from adapters.
376 // But they cannot.)
377
378 guarantee(is_stack_overflow ||
379 (cb->is_c2i_adapter() && ((C2IAdapter*)cb)->inlinecache_check_contains(pc)),
380 "exception happened outside interpreter, nmethods and vtable stubs (2)");