| Author |
Two kinds of Thread dumps
|
Marcelo Rodriguez
Greenhorn
Joined: Feb 28, 2008
Posts: 6
|
|
I recently learned how to read thread dumps, and when I tried to test my knowledge with a production problem, the customer sent me a thread dump with the following format:
I did not understand anything (where are the monitors? What is the memory address? Who is the current thread? and so on...), I am used to see something like this:
Was this generated from a specific application server's interface? Is there a way to diagnose the problem with the vague information from the first format ?
thanks in advance,
Marcelo
|
- The powerfull men can destroy one rose or two, they can even destroy the Spring (and Struts), but they will never defeat Java Server Faces (Only Tapestry can do that...) - 'Ctrl+C, Ctrl+V of Che Guevara Quote, with cH4n6Es'
|
 |
Henry Wong
author
Sheriff
Joined: Sep 28, 2004
Posts: 16681
|
|
Weblogic tries to rename the thread, with relevant data, such as the state. Other than that, the rest of the stack trace should be exactly the same -- except the name of the thread changes.
Henry
|
Books: Java Threads, 3rd Edition, Jini in a Nutshell, and Java Gems (contributor)
|
 |
Marcelo Rodriguez
Greenhorn
Joined: Feb 28, 2008
Posts: 6
|
|
So, are you saying that this is a 'thread dump' generated by weblogic that keep the information more 'simple'?
So, it's a matter of which JVM generated them, right?
I still believe that HotSpot, JRockit and IBM JVMs will produce different outputs/formats in their thread dumps, do you know the difference between them?
Thanks.
|
 |
 |
|
|
subject: Two kinds of Thread dumps
|
|
|