Make the script executable with chmod 755. Option 3: kill -3 Linux script (continuous)ĭownload either threaddump_linux-continuous.sh.tar.gz or threaddump_solaris-continuous.sh.tar.gz, and extract the script. threaddump_solaris.sh JAVA_PIDīe sure to test the script before the issue happens to make sure it runs properly in your environment.
#Access oracle after logging into unix on mac series#
The script will capture a series of 6 thread dumps spaced 20 seconds apart (this can be modified as needed), passing in the Java process ID as an argument. Option 2: kill -3 Linux script (not-continuous)ĭownload either threaddump_linux.sh.tar.gz or threaddump_solaris.sh.tar.gz, and extract the script. using top, a grep on ps -axw, etc.) and send a QUIT signal to the process with the kill -QUIT or kill -3 command 1. Note the process ID number of the Java process (e.g. Execute the following, passing in the Java process ID: jstack -l JAVA_PID > jstack.out it is not desirable to restart the JVM just to redirect standard out). This is useful when redirecting standard out to a file is problematic for some reason (e.g.
If using OpenJDK or Sun JDK 1.6 or later, using jstack is an option. Running kill -3 sends a SIGQUIT signal to the JVM, so using this option will cause kill -3 to be ignored. Use jps -lv to find the Java process ID for issuing kill -QUIT or kill -3.īe sure the -Xrs JVM option is not being used, as it causes SIGQUIT and SIGWAITING signals to be ignored. Excessive gc can cause threading issues, so gc and thread dump analysis go hand in hand. Note: Typically gc logging is provided whenever thread dumps are captured.
0 kommentar(er)
