Troubleshooting
Problem
When various types of problem occur, the Javadump is a useful to provide information about the general state of the Java runtime and the application running on it. In order to ensure this is generated the relevant settings must be in place. Although they are set by default it is possible that the default setting has been changed so it is important to check that the correct settings are in place.
Resolving The Problem
Check that the the JVM is set to produce a javadump file when a user signal (SIGQUIT) or GPF (General Protection Fault, for example: SIGSEGV) occurs, by adding the following command line option:
-Xdump:what
which shows the options which are set, such as:
dumpFn=doJavaDump
events=gpf+user+abort
filter=java/lang/OutOfMemoryError
label=/u/myuser/sdk/jre/bin/javacore.%Y%m%d.%H%M%S.%pid.txt
range=1..0
priority=10
request=exclusive
The above values are the default settings. At least events=gpf and events=user must be in place to generate javadumps on a crash or a user signal.
Options can be changed and/or set using the command line option:
-Xdump:java[:=,...]
So, for example, to set the ability to generate javadump files on user signals you would use:
-Xdump:java:events=user
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21222439