View post: ThreadDumps and StackTraces
Navigation
Recent posts from all feeds
- hSenid - officially certified JBCP partner
- jBPM 3 seam/jsf/richfaces based console
- Help push the open sourcing of a jBPM Migration Tool
- JBUG Munich meets Pete Muir with JSR-299 - Contexts and Dependency Injection for Java EE (06.07.09 at 19:00 PM)
- Javarsovia, static analysis and annotations
- Drools Job requested - Buenos Aires Argentina
- Seam and Web Beans downloads temporarily relocated
- Introducing a new smart forms tool: Drools Advisor
- JBoss Cloud introduction video
- Using rich:colorPicker in RichFaces
- « Back to feed: Dimitris' Thoughts
ThreadDumps and StackTraces
Thread Dumps and Stack Traces are useful tools for debugging java applications. In JBossAS there are several ways to get stacktraces, most common being to use the jmx-console. An entry point to the various techiques for taking thread dumps is this wiki page.Browsing the Java Specialists archive, I found yet another JSP-based threaddump utility. The difference with the thread dump you get with the jmx-console is that a sorted summary of the threads is presented in the beginning of the page, with links to the individual stacktraces that follow in the bottom of the page. The jmx-console in contrast shows the stacktraces inline with the list of threads, grouped according to their groupId and sorted by their threadId.
I adapted this for JBossAS and you can find it here.
Post to DZone
Post to del.icio.us
Digg this!
Stumble It!