Comments on: Java Thread Dump http://www.myloadtest.com/java-thread-dump/ Performance Testing with a LoadRunner focus Sat, 13 Mar 2010 03:31:20 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Anthony Hallett http://www.myloadtest.com/java-thread-dump/#comment-5548 Anthony Hallett Mon, 23 Apr 2007 00:33:44 +0000 http://www.myloadtest.com/?p=86#comment-5548 Good to see you back posting :-) Good to see you back posting

:-)

]]> By: Stuart Moncrieff http://www.myloadtest.com/java-thread-dump/#comment-5019 Stuart Moncrieff Tue, 10 Apr 2007 22:56:35 +0000 http://www.myloadtest.com/?p=86#comment-5019 Some additional points: · You may be able to generate a thread dump from the Admin Console of your application server. Under Unix, this is much simpler than doing a kill -3 from the shell, and it means that you do not have to be a member of the same group that the application server is a member of. · It is helpful to run multiple stack traces over a short period of time. If the same thread is still stuck at the same position of code, that is a good indication of a problem. This is a good thing to create a shell script for. · I quite liked this blog entry on stack traces and thread dumps: http://www.me.umn.edu/~shivane/blogs/cafefeed/2004/06/of-thread-dumps-and-stack-traces.html · Also, this one: http://java.sun.com/developer/technicalArticles/Programming/Stacktrace/ Some additional points:

· You may be able to generate a thread dump from the Admin Console of your application server. Under Unix, this is much simpler than doing a kill -3 from the shell, and it means that you do not have to be a member of the same group that the application server is a member of.
· It is helpful to run multiple stack traces over a short period of time. If the same thread is still stuck at the same position of code, that is a good indication of a problem. This is a good thing to create a shell script for.
· I quite liked this blog entry on stack traces and thread dumps: http://www.me.umn.edu/~shivane/blogs/cafefeed/2004/06/of-thread-dumps-and-stack-traces.html
· Also, this one: http://java.sun.com/developer/technicalArticles/Programming/Stacktrace/

]]> By: Stuart Moncrieff http://www.myloadtest.com/java-thread-dump/#comment-5018 Stuart Moncrieff Tue, 10 Apr 2007 22:45:55 +0000 http://www.myloadtest.com/?p=86#comment-5018 The Sun 1.5 JVM is able to detect some simple deadlocks. Using the example code from http://java.sun.com/docs/books/faq/src/thr/DeadlockExample.html the thread dump includes the following information: Found one Java-level deadlock: ============================= "Thread-1": waiting to lock monitor 0x00a891ec (object 0x06c216e0, a java.lang.String), which is held by "Thread-0" "Thread-0": waiting to lock monitor 0x00a8920c (object 0x06c21708, a java.lang.String), which is held by "Thread-1" The Sun 1.5 JVM is able to detect some simple deadlocks.

Using the example code from
http://java.sun.com/docs/books/faq/src/thr/DeadlockExample.html the thread dump includes the following information:

Found one Java-level deadlock:
=============================
“Thread-1″:
waiting to lock monitor 0×00a891ec (object 0×06c216e0, a java.lang.String),
which is held by “Thread-0″
“Thread-0″:
waiting to lock monitor 0×00a8920c (object 0×06c21708, a java.lang.String),
which is held by “Thread-1″

]]>