TDA - Thread Dump Analyzer

I just released Version 1.5 of my little tool TDA - Thread Dump Analyzer. This release includes: Added jconsole plugin support, TDA can now be used as jconsole plugin. Added ability to request thread dumps via JMX if running as jconsole plugin. JMX ... [More] Dumps can be saved into logfile for later offline usage. Session now can be stored to disk (and loaded again). expanded help overview. Major code cleanup. Improved memory footprint. Added splash-screen (JDK 1.6 only). Bugfixing. I want to especially point out the possibility to use TDA as JConsole plugin. Thread Dumps can be requested from a remote virtual machine using JMX. Fig 1. TDA as JConsole Plugin The requested thread dumps can be stored into a logfile for later offline analysis. See on tda.dev.java.net for further information, download package and webstart link. [Less]

I just released Version 1.5 of my little tool TDA - Thread Dump Analyzer. This release includes: Added jconsole plugin support, TDA can now be used as jconsole plugin. Added ability to request thread dumps via JMX if running as jconsole plugin. ... [More] JMX Dumps can be saved into logfile for later offline usage. Session now can be stored to disk (and loaded again). expanded help overview. Major code cleanup. Improved memory footprint. Added splash-screen (JDK 1.6 only). Bugfixing. I want to especially point out the possibility to use TDA as JConsole plugin. Thread Dumps can be requested from a remote virtual machine using JMX. Fig 1. TDA as JConsole Plugin The requested thread dumps can be stored into a logfile for later offline analysis. See on tda.dev.java.net for further information, download package and webstart link. [Less]

I've just added support to my little TDA tool for running it as a JConsole plugin. You can use JConsole to remotely connect to an Java 1.5 or 1.6 VM. The TDA plugin can be used to request thread dumps from the connected VM which are then parsed and ... [More] displayed in the thread dumps tab in JConsole. Fig 1. TDA as JConsole Plugin The requested dumps also can be stored to a logfile for later offline parsing. A first beta of the next release 1.5 of TDA including the JConsole Plugin support can be downloaded at tda.dev.java.net. You should have a JDK 1.6 installed on the client side for testing it. JDK 1.5 also works, but 1.6 is easier to use. The remote VM can either be a 1.5 or 1.6 VM. Use the following to add the plugin to JConsole: jconsole -pluginpath ./tda.jar See Application Analysis using jconsole for information on how to set up a remote VM for accessing it via JMX. Report bugs and suggestions here. [Less]

I've just added support to my little TDA tool for running it as a JConsole plugin. You can use JConsole to remotely connect to an Java 1.5 or 1.6 VM. The TDA plugin can be used to request thread dumps from the connected VM which are then parsed and ... [More] displayed in the thread dumps tab in JConsole. Fig 1. TDA as JConsole Plugin The requested dumps also can be stored to a logfile for later offline parsing. A first beta of the next release 1.5 of TDA including the JConsole Plugin support can be downloaded at tda.dev.java.net. You should have a JDK 1.6 installed on the client side for testing it. JDK 1.5 also works, but 1.6 is easier to use. The remote VM can either be a 1.5 or 1.6 VM. Use the following to add the plugin to JConsole: jconsole -pluginpath ./tda.jar See Application Analysis using jconsole for information on how to set up a remote VM for accessing it via JMX. Report bugs and suggestions here. [Less]

This release includes: Full logfile is added as node (loaded up to specified size). Added Thread Dump navigation into logfile. Improved Deadlock analysis, additional hints concerning deadlocks found be JVM. Fixed Issue 5. Added ... [More] toolbar (can be switched off). Improved GTK Display for recent JDKs. Bugfixing. Java Webstart is available here and downloadable zip is available here. [Less]

This release includes: Full logfile is added as node (loaded up to specified size). Added Thread Dump navigation into logfile. Improved Deadlock analysis, additional hints concerning deadlocks found be JVM. Fixed Issue 5. Added ... [More] toolbar (can be switched off). Improved GTK Display for recent JDKs. Bugfixing. Java Webstart is available here and downloadable zip is available here. [Less]

There is a new version of the HeapAnalyzer for IBM VMs out. This version just includes some small fixes. But because I haven't mentioned this tool so far, I post it here. It can be downloaded on IBM alphaworks. There is also a interesting podcast ... [More] with slides available from the developer of the tool explaining it in detail. The Analyzer supports IBM and SUN JVMs, for SUN JVM I would suggest to use the SAP Memory Analyzer though as it offers a lot more features and needs less memory. HeapAnalyzer's features include: List of Java heap leak suspects, Recommendation of the size of kCluster, List of gaps among allocated objects/classes/arrays, Java objects/classes/arrays search engine, List of objects/classes/arrays by different sort criteria like object name, size, etc., List of available heap spaces by size, Tree view of Java heap dump, Loading/saving processed Java heap dumps. Fig 1. IBM HeapAnalyzer 2.2 displaying heap dump information I tested the tool with a heap dump generated by a IBM JDK 1.6 Beta VM. It offers a lot of statistics about the heap dump and an heap walker, where you can look what is inside the dump. Unlike the SAP Memory Analyzer it doesn't offer a retained size calculation which helps you finding memory leaks. Update: A short test showed the tool is also able to parse head dumps of Sun VMs. But compared to the SAP Memory Analyzer it needs a lot more memory and offers less features (like the missing, very handy "retained size"). [Less]

There is a new version of the HeapAnalyzer for IBM VMs out. This version just includes some small fixes. But because I haven't mentioned this tool so far, I post it here. It can be downloaded on IBM alphaworks. There is also a interesting podcast ... [More] with slides available from the developer of the tool explaining it in detail. The Analyzer supports IBM and SUN JVMs, for SUN JVM I would suggest to use the SAP Memory Analyzer though as it offers a lot more features and needs less memory. HeapAnalyzer's features include: List of Java heap leak suspects, Recommendation of the size of kCluster, List of gaps among allocated objects/classes/arrays, Java objects/classes/arrays search engine, List of objects/classes/arrays by different sort criteria like object name, size, etc., List of available heap spaces by size, Tree view of Java heap dump, Loading/saving processed Java heap dumps. Fig 1. IBM HeapAnalyzer 2.2 displaying heap dump information I tested the tool with a heap dump generated by a IBM JDK 1.6 Beta VM. It offers a lot of statistics about the heap dump and an heap walker, where you can look what is inside the dump. Unlike the SAP Memory Analyzer it doesn't offer a retained size calculation which helps you finding memory leaks. Update: A short test showed the tool is also able to parse head dumps of Sun VMs. But compared to the SAP Memory Analyzer it needs a lot more memory and offers less features (like the missing, very handy "retained size"). [Less]

VisualVM is a tool for analyzing and profiling running java applications. There is first preview release available showing a subset of the planned features. It is based on the netbeans platform and utilizes the netbeans profiler and the jstat tool ... [More] from the SUN Java VM. The preview release can be downloaded from dev.java.net. There is also a short introduction on how to use the tool available. Currently the VisualVM preview release offers: Ability to connect to java processes running with either SUN JDK 1.5 or 1.6 VMs. Request thread dumps from a java process running locally. Display heap information like heap utilization and permanent space usage (see screenshot below). Basic heap dump visualization (from the netbeans profiler). Basic profiling of running processes (also using the netbeans profiler). Remote connection to Java processes using the jstatd demon. Fig 1. VisualVM displaying heap information There are no information available about the planned features but as the application has a node called "VM core dumps" parsing of core dumps from crashed Java VMs seems to be a planned feature. The features of the preview are very basic at the moment. Instead of using JVMTI or JMX for connections to the application vm it uses jstat, which might be easier to set up on a production environment as it usually doesn't require any changes to the VM, I tested it with an Oracle ApplicationServer 10.1.3 instance using ./jstatd -J-Djava.security.policy=all.policy to provide access to it. The used policy file is grant codebase "file:${java.home}/../lib/tools.jar" { permission java.security.AllPermission; }; Requesting remote heap and thread dumps seems not to be implemented so far, only for applications running locally. [Less]

VisualVM is a tool for analyzing and profiling running java applications. There is first preview release available showing a subset of the planned features. It is based on the netbeans platform and utilizes the netbeans profiler and the jstat tool ... [More] from the SUN Java VM. The preview release can be downloaded from dev.java.net. There is also a short introduction on how to use the tool available. Currently the VisualVM preview release offers: Ability to connect to java processes running with either SUN JDK 1.5 or 1.6 VMs. Request thread dumps from a java process running locally. Display heap information like heap utilization and permanent space usage (see screenshot below). Basic heap dump visualization (from the netbeans profiler). Basic profiling of running processes (also using the netbeans profiler). Remote connection to Java processes using the jstatd demon. Fig 1. VisualVM displaying heap information There are no information available about the planned features but as the application has a node called "VM core dumps" parsing of core dumps from crashed Java VMs seems to be a planned feature. The features of the preview are very basic at the moment. Instead of using JVMTI or JMX for connections to the application vm it uses jstat, which might be easier to set up on a production environment as it usually doesn't require any changes to the VM, I tested it with an Oracle ApplicationServer 10.1.3 instance using ./jstatd -J-Djava.security.policy=all.policy to provide access to it. The used policy file is grant codebase "file:${java.home}/../lib/tools.jar" { permission java.security.AllPermission; }; Requesting remote heap and thread dumps seems not to be implemented so far, only for applications running locally. [Less]