IBM Tivoli Composite Application Manager for Application Diagnostics, Version 188.8.131.52
Control Instrumentation of Application Classes for Memory Leak, Lock and L3 Method Analysis - J2EE Agent
ITCAM for J2EE uses a technique called Byte Code Instrumentation (BCI) to collect Level 3 tracing data, Memory Leak Diagnosis data, and Lock Contention data from your applications. BCI is enabled by making adjustments to the properties in the custom_directory/toolkit_custom.properties file.
Make these adjustments will activate 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:
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.
To enable one or more of the BCI features with the default settings, see Enable BCI features with default settings.
To customize the default settings and make more granular choices for what classes and methods to modify, see one or more of the following sections:
- Enable BCI features with default settings
- Customize L3 Method Entry and Exit Analysis
To enable L3 method entry and exit analysis with customized settings:
- Customize Memory Leak Diagnosis
To enable Memory Leak Diagnosis with customized settings:
- Customize Lock Analysis
Perform the following procedure enable lock analysis with customized settings:
Parent topic:Customization and advanced configuration for the data collector