NonStop Server for Java 7.0 Programmer's Reference

Example 10 The following is the first few lines of the error log file when a Java process with parallel
or concurrent GC terminates abnormally
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=7ed16ab4, pid=1979711505, tid=10 # # JRE version: 7.0 # Java VM: Java HotSpot(TM) Server
VM (21.1-b02-svcnedccadmin:2012jul25-11:47 mixed mode nsk oss-ia64 ) # Problematic frame:
# C [(DLL libjvm.so)+0x0] invoke__17PSParallelCompactSFb + 0x1C0 (DLL libjvm.so)+0x0 #
This example indicates that the hs_err_pid1979711505_1979711505.log file was created
by a Java process with PID 1979711505, and that it terminated due to SIGSEGV.
Example 11 The following is the first few lines of the error log file when a GC process terminated
after detecting the abnormal termination of another process in the Java process group
#
# A fatal error has been detected by the Java Runtime Environment:
#
# Internal Error (0xe0000010), pid=2097152069, tid=4 # Error: Process 3,1140 in the Java process group has
terminated abnormally. Initiating termination of all the other processes in the process group # # JRE version:
7.0 # Java VM: Java HotSpot(TM) Server VM (21.1-b02-svcnedccadmin:2012jul25-11:47 mixed mode nsk oss-ia64 ) #
Failed to write core dump.
#
# Please report this error to HP customer support.
#
----------- P R O C E S S G R O U P-------------
# The processes in the Java process group are:
# PID (CPU, PIN):
# 620757051 (3,1138)
# 1006633021 (3,1141)
# 2097152069 (3,1139)
# 1291845689 (3,1144)
# 1979711505 (3,1140)
This example indicates that GC process with PID 2097152069 created the file
hs_err_pid1979711505_2097152069.log. The log indicates that the GC process had
terminated due to another process in the Java process group terminating abnormally. The Java PID
corresponding to this GC process is 1979711505. There are four GC processes in the Java group
and their PIDs are 620757051, 1006633021, 2097152069, and 1291845689.
ErrorFile with %p option
The product flag —XX:ErrorFile=file can be used to specify where the error log file is created.
Where, file represents the full path for the file location. The file variable can contain the substring
%p.
If the application uses Serial GC and a fatal error occurs, the substring %p is expanded to process
ID of the Java process.
If the application uses Parallel or CMS GC and a fatal error occurs, the substring %p is expanded
to <Java PID>_<[Java PID| GC PID]>.
Where, <Java PID> is the process ID of the Java process ID and <GC PID> is the process ID
of the GC process.
The first process ID is always the Java process ID. The second process ID is the process ID of the
process that creates the error file. If the error file is created by the Java process, the second process
ID is the Java process ID and if created by the GC process, it is the GC process ID. The number
of error files created is equal to the number of processes in the Java process group. This is illustrated
by the following examples:
68 Implementation specifics