This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
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,
- 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'
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?
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com