IBM Tivoli Composite Application Manager for Application Diagnostics, Version

Lock analysis, memory leak analysis, and method profiling and tracing

The data collector can use Byte Code Instrumentation (BCI) to collect lock analysis information, memory leak analysis information (at MOD L3), method profiling (at MOD L2) and application method entry and exit (at MOD L3). Instrumentation for this data is disabled by default.

This information is only displayed in the Visualization Engine of ITCAM for Application Diagnostics Managing Server.

To enable BCI for lock analysis, Level 3 memory leak analysis, and Level 3 method entry and exit tracing, make adjustments to the toolkit custom properties file.

Making these adjustments will activate the use of one or more configuration files in...

...which contain the default settings to control BCI.

Configuration files and default settings include...

File name Purpose Default behavior
lock_analysis.xml Application lock analysis Specific behavior in each MOD level is determined by settings in the data collector properties file. Lock acquire and release requests for all application classes are Byte-Code-Instrumented. Lock event, lock contention, and lock reporting information is provided in MOD L2 and MOD L3. You can enable lock analysis for MOD L1 as well.
memory_leak_diagnosis.xml Application Memory Leak Diagnosis Heap allocations for all classes instantiated by all application classes are Byte-Code-Instrumented. Leak Analysis data is collected at MOD L3.
method_entry_exit.xml Application method entry and exit All non-trivial methods for all application classes, subject to certain thresholds and limits, are Byte-Code-Instrumented. Method profiling data is collected at MOD L2; method entry and exit analysis data is collected at MOD L3.

Enabling Byte Code Instrumentation for any of these features will slightly increase resource usage even on monitoring levels where no data is collected for them.

Parent topic:

Tune data collector performance and monitoring scope