IBM Tivoli Composite Application Agent for J2EE, Version 7.1.1

Controlling Instrumentation of Application Classes for Memory Leak, Lock, and L3 Method Analysis

ITCAM for J2EE uses a technique called Byte Code Instrumentation (BCI). BCI collects Level 3 tracing data, Memory Leak Diagnosis data, and Lock Contention data from your applications. BCI is enabled by adjusting properties in the custom_directory/toolkit_custom.properties file.

Making these adjustments activates the use of one or more configuration files in the DC_home/itcamdc/etc directory, which contain the default settings to control BCI. The configuration files are described in the following table:

Table 1. BCI Configuration Files
File Name	Purpose	Default Behavior
method_entry_exit.xml	Defines application method entry and exit BCI	All non-trivial methods for all application classes are Byte-Code-Instrumented for method entry and exit analysis.
memory_leak_diagnosis.xml	Defines application Memory Leak Diagnosis BCI	Heap allocations for all classes instantiated by all application classes are Byte-Code-Instrumented.
lock_analysis.xml	Defines application lock analysis BCI	Lock acquire and release requests for all application classes are Byte-Code-Instrumented.

If you want to enable one or more of the BCI features with the default settings, see Enabling BCI features with default settings.

If you want to customize the default settings and choose what classes and methods to modify, see one or more of the following sections:

Feedback