NonStop Server for Java 7.0 Programmer's Reference

SIGINT
JVM uses this signal to support shut down hook if —Xrs is not specified in the command line option
(reduce signal usage). If –Xrs is specified in the command line option, the application can install
signal handlers for SIGINT signal.
SIGTERM
JVM uses this signal to support shut down hook if —Xrs is not specified in the command line option
(reduce signal usage). If –Xrs is specified in the command line option, the application can install
signal handlers for SIGTERM signal.
Unhandled exception
If Distributed Garbage Collector (DGC) is enabled and a Java or its GC processes encounter
unhandled exception, the process which encounters the exception terminates. The other processes
in the process group detect the termination of the process and exit abnormally.
Error file
When a fatal error occurs, one or more error log file are created depending upon the type of GC
used by the application.
If the application uses Serial GC and a fatal error occurs, only one error file is created and it is
in the form hs_err_pid<pid>.log
where,
<pid> is the process ID of the Java process. This is the same format of the error file created in
earlier version of NSJ.
If the application uses Parallel or Concurrent GC and a fatal error occurs, more than one fatal
error files are created and their filename format is of the form hs_err_pid<Java pid>_<Java
pid | GC pid>.log
where,
<Java pid> is the process ID of the Java process 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.
When a fatal error occurs, the process that encounters the fatal error terminates. The header of
the error log file generated by this process contains information about the fatal error. This could
be an operating system signal or a JVM internal error. If Parallel or Concurrent GC is used, other
processes in the Java process group also terminate and create error log files as mentioned earlier.
The error log file contains additional information about the process that encountered the fatal error
and the list of processes that forms the Java group.
Thus, the process that encountered the fatal error can be identified by looking at the headers of
all the error log files generated.
Unhandled exception 67