0% found this document useful (0 votes)
37 views3 pages

Full Core Dump

full core dump
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
37 views3 pages

Full Core Dump

full core dump
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 3

Setting up the generation of diagnostic data for a crash Setting up the generation of diagnostic data for a crash Introduction

If the Java runtime crashes with a SIGSEGV or SIGKILL message, or a General Protection Fault (GPF), three sources of information help you to diagnose the pr oblem: System dump generation Javacore generation IBM Monitoring and Diagnostic Tools for Java - Diagnostics Collector ins talled and configured Ensuring that system dump generation is enabled To generate full system dumps of core or minidump files, check the following : (AIX and Linux) ulimit setting configuration (AIX only) SMIT setting configuration JVM dump generation configuration Disk space availablity (AIX and Linux) Configuring the ulimit setting Use one of the following commands: ulimit -c unlimited ulimit -n unlimited ptors ulimit -u unlimited ulimit -f unlimited sets the user memory limit to unlimited sets the file limit to unlimited turn on corefiles with unlimited size allows an unlimited number of open file descri

The current ulimit settings can be displayed using: ulimit -a These values displayed are for the soft limit, and are provided on a per user basis. The limits cannot exceed the hard limit value. To display or change the hard limits, use the same ulimit commands with the -H option. For example, to display the current hard limits, enter the command: ulimit -H -a (AIX only) SMIT setting configuration Start smit by typing smit as root. Go to System Environments -> Change/Show Characteristics of Operatin g System. Set the Enable full CORE dump option to TRUE. You can also set TRUE by running chdev -l sys0 -a fullcore='true' as root.

Check that the option is enabled by using the command: lsattr -D -c sys -a fullcore -H The command produces output similar to the following: attribute deflt description user_settable fullcore false Enable full CORE dump True JVM dump generation configuration Check that the JVM is set to produce a core file when a crash occurs. Ru n the following command: java -Xdump:what The command produces output similar to the following: dumpFn=doSystemDump events=gpf+abort filter= label=c:\username\sdk\jre\bin\core.%Y%m%d.%H%M%S.%pid.dmp range=1..0 priority=999 request=nodumps The values shown are the default settings. To generate a core file when a crash occurs, set the option events=gpf. You can change or set options with th e command-line option: java -Xdump:system[:=, ...] Disk space availability The JVM can write the crash dump file to any directory specified in the label option. Enough disk space must be available to write the crash dump file. The Java process must have the correct permissions to write to that location. Th e system dump file from a process is often the same size as the process it came from. For a 32-bit process, the system dump can be up to 3.5 GB in size. For a 6 4-bit process, the system dump might be significantly larger. Ensuring that javadump file generation is enabled Check that the JVM is set to produce a javadump file when a user signal such as SIGQUIT is sent or when a General Protection Fault such as SIGSEGV occurs. U se this command-line option:

-Xdump:what This option shows you which options are set; for example: dumpFn=doJavaDump events=gpf+user+abort filter= 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. To generate javadumps on a crash or a user signal, the options events=gpf and events=user must be in place. Value s can be changed or set using the command-line option: -Xdump:java[:=,...] For example, to generate javadump files on user signals, use the following o ption: -Xdump:java:events=user Ensuring that the IBM Monitoring and Diagnostic Tools for Java - Diagnostics Col lector is installed and configured The IBM Monitoring and Diagnostic Tool for Java - Diagnostics Collector auto mates the collection of most of the data that is required when a crash occurs. I nformation on how to download, install, and configure Diagnostics Collector is a vailable here: http://www-01.ibm.com/support/docview.wss?uid=swg24019419 Setting up the generation of diagnostic data for a crash Re-create required After configuring your application to generate diagnostics data, re-create your problem and collect the data that is generated.

You might also like