|  |
Diagnostic Tool for Java Garbage Collector
A diagnostic tool for optimizing parameters affecting the garbage collector when using the IBM Java Virtual Machine.
Date Posted: December 16, 2004
|
|
 |
 |
|
Platform requirements for Diagnostic Tool for Java Garbage Collector
Operating systems: Any platform with a Java Run-time Environment installed (JRE 1.3 or above)
Java tools:
- JRE 1.2.2 or above
- Two Java libraries in JFreeChart, Version 1.0.0-rc1; available in SourceForge.net (extract from jfreechart-1.0.0-rc1.zip) or on the JFreeChart project home page):
- jfreeChart-1.0.0-rc1.jar
- jcommon-1.0.0-rc1.jar
Installation instructions for Diagnostic Tool for Java Garbage Collector
- Obtain two Java libraries in JFreeChart, Version 1.0.0-rc1 (jfreeChart-1.0.0-rc1.jar and jcommon-1.0.0-rc1.jar) in either of these two ways:
- Extract the contents of GCCollector.zip in a directory of your chioce.
- Place jfreeChart-1.0.0-rc1.jar and jcommon-1.0.0-rc1.jar in the lib directory that was created when you unzipped GCCollector.zip.
- In order to run Diagnostic Tool for Java Garbage Collector, execute GCCollector.bat, which is located in the directory where you unzipped GCCollector.zip.
Notes:
- The file GCCollector.bat is an example of how to execute Diagnostic Tool for Java Garbage Collector; you may need to adapt it to your environment. The javaw command in the file has the parameter "-Xmx300m", which sets the maximum Java heap size to 300 MB. This should be enough for working with more than ten thousand garbage collection cycles; please feel free to modify the Xmx parameter if you experience Out of memory errors.
- In the same directory, you will find two sample files: sample150_stderr.log and sample142_stderr.log; they should be useful if you want to try Diagnostic Tool for Java Garbage Collector but don't have your own verbose collection data file.
|
|
 |
|
View screenshots:
 |
| |
|