The Agent Controller distributed with the 6.0.1 version of this product supports a new format for Optimized heap dumps used in leak analysis. The heap file format and naming convention are simplified. Prior to this release, the heap files were in sets, with a header file and alternating heap files and move/free files where multiple files were needed to process each heap. In 6.0.1, the header file and the move and free files are no longer generated, each captured heap is stored in a single, stand-alone file, and the file naming is changed to match the naming for the heap dumps generated by IBM JVMs. The new Optimized heap name format is:
<prefix=optHeap>.<date>.<time when heap is taken>.<pid of System Under Test>.<suffix=trcopt>
A sample set of 4 6.0.1 Optimized heap files:
optHeap.20050318.143056.3000.trcopt optHeap.20050318.143102.3000.trcopt optHeap.20050318.143107.3000.trcopt optHeap.20050318.143110.3000.trcopt
The easiest way to identify the old and new files is through their suffixes. The old files have suffix of ".trchoh" and the new ones ".trcopt".
It is best to use the 6.0.1 Agent Controller distributed for collecting Optimized heap dumps for leak analysis in 6.0.1. In situations where that is not possible, and to support heaps generated with older releases, the 6.0.1 refresh pack includes limited support for old style Optimzed heap files.
You can connect to and capture old style heaps using the Automatic Leak Detection Profiling Set. You will get warning messages, alerting you about the older Agent Controller. You may choose to proceed and capture old style Optimized heaps. Once the heaps are captured, you must make the heaps available to the processor where this product is running. This may involve copying the heaps from the processor where the Agent Controller and the System Under Test are running to the processor where this product is running.
Once the heaps are reachable from a file browser, run "Import > Heaps" to bring the heaps into a Profiling Project. This creates a new process entry in the Profiling Project, converts the heaps to the new format and saves the new heaps in the leakanalysis subdirectory in the project directory. Run leak analysis or open views on the converted heaps displayed in the Profiling Monitor. After conversion, the old format heaps are not accessed.
Use the same "Import > Heaps" wizard to bring any existing old format heap files into a Profiling Project. This is the only supported path for older heap files. Other ways of getting data into a 6.0.1 workspace, such as "Import > Existing Project into Workspace", are not supported.
Symptom 1: Occasionally, Import > Heap dump succeeds, but the heap dump does not show up in the Profiling Monitor.
Symptom 2: When profiling an application for leak analysis, "Capture Heap dump" causes a heap dump object to appear under the agent, but then displays <Waiting to transfer data> forever.
Either of the above symptoms may be because of problems related to firewalls such as Zone Labs Integrity Desktop. Please disable any firewall that you may be running on the workbench machine. And retry the operation.
Return to the main readme file
©Copyright IBM Corporation 2000, 2005. All Rights Reserved.