|
(→kill)
|
(Added more spacing. Previous format looked like shit.)
|
| Line 2: | |||
| On versions 3.7.5+, you should be able to get an anthill-specific thread dump by navigating to System --> Server Settings --> Diagnostics --> View CPU Thread Usage. | On versions 3.7.5+, you should be able to get an anthill-specific thread dump by navigating to System --> Server Settings --> Diagnostics --> View CPU Thread Usage. | ||
| + | <br/> | ||
| = Windows = | = Windows = | ||
| This section lists methods to obtain fresh dumps on Windows-based platforms | This section lists methods to obtain fresh dumps on Windows-based platforms | ||
| Line 7: | |||
| + | <br/> | ||
| == All Java Versions == | == All Java Versions == | ||
| + | <br/> | ||
| === Thread Dump From Console Window === | === Thread Dump From Console Window === | ||
| + | |||
| Line 13: | |||
| + | <br/> | ||
| === Thread Dump From a Windows Service === | === Thread Dump From a Windows Service === | ||
| Line 19: | |||
| Run this from an ''administrative command prompt''. You want to make the time 1 minute ahead of your current time and the ^ characters critical as they are the cmd.exe escape character. If you run it after the time has elapsed, it will run the next day instead, so be careful. You can run "at" without options to make sure your command is scheduled appropriately. | Run this from an ''administrative command prompt''. You want to make the time 1 minute ahead of your current time and the ^ characters critical as they are the cmd.exe escape character. If you run it after the time has elapsed, it will run the next day instead, so be careful. You can run "at" without options to make sure your command is scheduled appropriately. | ||
| + | <br/> | ||
| == Java 6 == | == Java 6 == | ||
| There may be different options for each type of Java installed. The commands listed below are known to work with the Java 6 JDK. | There may be different options for each type of Java installed. The commands listed below are known to work with the Java 6 JDK. | ||
| Line 24: | |||
| + | <br/> | ||
| === jstack (Thread Dump) === | === jstack (Thread Dump) === | ||
| Using 'jstack', which is part of the JDK, you can run: | Using 'jstack', which is part of the JDK, you can run: | ||
| Line 31: | |||
| This command will then take a thread dump of the java process specified and dump it to the console. You may want to consider redirecting this output to a file with the ''>'' modifier. | This command will then take a thread dump of the java process specified and dump it to the console. You may want to consider redirecting this output to a file with the ''>'' modifier. | ||
| + | <br/> | ||
| == Java 7 == | == Java 7 == | ||
| There may be different options for each type of Java installed. The commands listed below are known to work with the Java 7 JDK. | There may be different options for each type of Java installed. The commands listed below are known to work with the Java 7 JDK. | ||
| Line 36: | |||
| + | <br/> | ||
| === jstack (Thread Dump) === | === jstack (Thread Dump) === | ||
| Using 'jstack', which is part of the JDK, you can run: | Using 'jstack', which is part of the JDK, you can run: | ||
| Line 43: | |||
| This command will then take a thread dump of the java process specified and dump it to the console. You may want to consider redirecting this output to a file with the ''>'' modifier. | This command will then take a thread dump of the java process specified and dump it to the console. You may want to consider redirecting this output to a file with the ''>'' modifier. | ||
| + | <br/> | ||
| === jmap (Heap Dump) === | === jmap (Heap Dump) === | ||
| Using 'jmap', which is part of the JDK, you can run: | Using 'jmap', which is part of the JDK, you can run: | ||
| Line 51: | |||
| + | <br/> | ||
| = *nix = | = *nix = | ||
| This section lists methods to obtain dumps on *nix-based platforms | This section lists methods to obtain dumps on *nix-based platforms | ||
| Line 56: | |||
| + | <br/> | ||
| == All Java Versions == | == All Java Versions == | ||
| + | <br/> | ||
| === kill === | === kill === | ||
| The 'kill' command on *nix machines will invoke a thread dump when the highest level of killing a process is inflicted. To perform the highest level of kill, and to generate a thread dump of the process that is being eradicated, run the following command: | The 'kill' command on *nix machines will invoke a thread dump when the highest level of killing a process is inflicted. To perform the highest level of kill, and to generate a thread dump of the process that is being eradicated, run the following command: | ||
| Line 65: | |||
| '''NOTE: -9 WILL TERMINATE PROCESS. USE -3 IF PROCESS TERMINATION IS NOT DESIRED.''' ''(see [[Comments:Dumps From a Java Process]] page)'' | '''NOTE: -9 WILL TERMINATE PROCESS. USE -3 IF PROCESS TERMINATION IS NOT DESIRED.''' ''(see [[Comments:Dumps From a Java Process]] page)'' | ||
| + | <br/> | ||
| == Java 5 == | == Java 5 == | ||
| There may be different options for each type of Java installed. The commands listed below are known to work with the Java 5 JDK. | There may be different options for each type of Java installed. The commands listed below are known to work with the Java 5 JDK. | ||
| Line 70: | |||
| + | <br/> | ||
| === jmap (Heap Dump) === | === jmap (Heap Dump) === | ||
| Using 'jmap', which is part of the JDK, you can run one of the following commands: | Using 'jmap', which is part of the JDK, you can run one of the following commands: | ||
| Line 79: | |||
| This command will then dump a summary of the current memory map to the console. While not as sophisticated as the later versions of java, it still provides some rudimentary functionality. | This command will then dump a summary of the current memory map to the console. While not as sophisticated as the later versions of java, it still provides some rudimentary functionality. | ||
| + | <br/> | ||
| === jstack (Thread Dump) === | === jstack (Thread Dump) === | ||
| Using 'jstack', which is part of the Java 5 JDK, you can run: | Using 'jstack', which is part of the Java 5 JDK, you can run: | ||
| Line 86: | |||
| This command will then take a thread dump of the java process specified and dump it to the console. It will only provide both Java & C/C++ threads during the trace. You may want to consider redirecting this output to a file with the ''>'' modifier. | This command will then take a thread dump of the java process specified and dump it to the console. It will only provide both Java & C/C++ threads during the trace. You may want to consider redirecting this output to a file with the ''>'' modifier. | ||
| + | <br/> | ||
| == Java 6 == | == Java 6 == | ||
| There may be different options for each type of Java installed. The commands listed below are known to work with the Java 6 JDK. | There may be different options for each type of Java installed. The commands listed below are known to work with the Java 6 JDK. | ||
| Line 91: | |||
| + | <br/> | ||
| === jmap (Heap Dump) === | === jmap (Heap Dump) === | ||
| Using 'jmap', which is part of the JDK, you can run: | Using 'jmap', which is part of the JDK, you can run: | ||
| Line 96: | |||
| This command will then dump the memory map of the target process-id# to an hprof file within the current directory (or specified directory if you expand on 'filename'). | This command will then dump the memory map of the target process-id# to an hprof file within the current directory (or specified directory if you expand on 'filename'). | ||
| + | <br/> | ||
| === jstack (Thread Dump) === | === jstack (Thread Dump) === | ||
| Using 'jstack', which is part of the JDK, you can run: | Using 'jstack', which is part of the JDK, you can run: | ||
| Line 105: | |||
| This command will then take a thread dump of the java process specified and dump it to the console. You may want to consider redirecting this output to a file with the ''>'' modifier. | This command will then take a thread dump of the java process specified and dump it to the console. You may want to consider redirecting this output to a file with the ''>'' modifier. | ||
| + | <br/> | ||
| == Java 7 == | == Java 7 == | ||
| There may be different options for each type of Java installed. The commands listed below are known to work with the Java 7 JDK. | There may be different options for each type of Java installed. The commands listed below are known to work with the Java 7 JDK. | ||
| Line 110: | |||
| + | <br/> | ||
| === jmap (Heap Dump) === | === jmap (Heap Dump) === | ||
| Using 'jmap', which is part of the JDK, you can run: | Using 'jmap', which is part of the JDK, you can run: | ||
| Line 115: | |||
| This command will then dump the memory map of the target process-id# to an hprof file within the current directory (or specified directory if you expand on 'filename'). | This command will then dump the memory map of the target process-id# to an hprof file within the current directory (or specified directory if you expand on 'filename'). | ||
| + | <br/> | ||
| === jstack (Thread Dump) === | === jstack (Thread Dump) === | ||
| Using 'jstack', which is part of the JDK, you can run: | Using 'jstack', which is part of the JDK, you can run: | ||
| Line 125: | |||
| + | <br/> | ||
| = References = | = References = | ||
