JAVA Thread Dumps Trilogy

First, the Windows environment method

1:cmd find the PID running the server container

Jps-v

Cases:

C:\users\administrator>jps-v
4856 Bootstrap-djdk.tls.ephemeraldhkeysize=2048-djava.util.logging.config.file
=d:\soft\apache-tomcat-7.0.69\conf\logging.properties-djava.util.logging.manage
R=org.apache.juli.classloaderlogmanager-djava.endorsed.dirs=d:\soft\apache-tomc
At-7.0.69\endorsed-dcatalina.base=d:\soft\apache-tomcat-7.0.69-dcatalina.home=
D:\soft\apache-tomcat-7.0.69-djava.io.tmpdir=d:\soft\apache-tomcat-7.0.69\temp
2896-xmx768m-xx:maxpermsize=320m-xx:reservedcodecachesize=64m-dosgi.nls.war
Nings=ignore
4136 jps-denv.class.path=.; C:\Program Files\java\jdk1.7.0_80\lib\dt.jar; C:\Prog
Ram Files\java\jdk1.7.0_80\lib\tools.jar; -dapplication.home=c:\program Files\ja
Va\jdk1.7.0_80-xms8m

2: Enter information into the log

Jstack-l 4856 >stack.out

The above found PID is 4856.

3: Run IBM Thread and Monitor Dump Analyzer for Java analysis

IBM Thread and Monitor Dump Analyzer for Java

JAVA Thread Dumps Trilogy