Java replay log, diagnosing an error in memory

Question

We are launching a Java 8 application with a JNI layer that crashed due to Out of Memory Errorsomewhere in layer C.

Along with the regular hs_err_pid.log file, this time we noticed that we also got the replay_pid.log file. I made some extensive google-foo and can hardly find anything about this file.

Has anyone seen this file before, and does anyone know what it contains and how best to analyze it?

Answer 1

The file is generated by the java hotspot to provide information on actions when a problem occurs. Regardless of whether it gives you something specific, to tell you where the problem seems to have hit or missed, but it helps to tell you what was going on overall at that time.

OpenJDK has discovered a similar issue with a play file that is generated after a segmentation error occurs. Allegedly, the problem was fixed with a later build, so if you are using a version smaller than 8u40, I would update and see if this fixes the problem. ( issue reported )

, C/++, , . JNI, ( , ), Java JNI C/++, , , Java . . C/++, , , .

Answer 2

, , "" ciReplay.cpp, . http://hg.openjdk.java.net/jdk8u/jdk8u/hotspot/file/849eb7bfceac/src/share/vm/ci/ciReplay.cpp.

389 (void process_command), , .

: - , . http://cr.openjdk.java.net/~minqi/6830717/raw_files/new/agent/doc/

:

GUI , API- HotSpot, HSDB, " HotSpot". , "hsdbproc.sh" "hsdbwindbg.bat" 64- ( Unix, Windows ). . HSDB GUI hsdb.html.

: http://hg.openjdk.java.net/hsx/hsx25/hotspot/file/0c94c41dcd70/agent/doc/cireplay.html http://hg.openjdk.java.net/hsx/hsx25/hotspot/file/0c94c41dcd70/agent/doc

, , , ...