Long time ago, when I was a BEA Senior Tech Support, Java stack traces (thread dumps) were often the only way to troubleshoot the situation. So, I built a tool

Long time ago, when I was a BEA Senior Tech Support, Java stack traces (thread dumps) were often the only way to troubleshoot the situation. So, I built a tool that took multiple versions of thread dumps (IBM vs Sun vs. JRocket vs different version) and converted them to normalized XML. Then, I visualized those individual threads within a thread dump with cross-references on the locks held. Made it 100 times easier to figure out dead- and live-locks. I also did a pretty-printed side-by side reports of the same thread across multiple thread-dumps. It was interesting enough that it was used within my group, I did a presentation on JavaONE about it and published in (now dead) Weblogic Developer's journal. Never managed to open-source it (the code was really ugly). Wish I did. People I sent it to during my tech support days kept using it in very large companies even after I left BEA.