IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

Problems with method trace

The following content provides solutions to some problems with method trace.


Method trace captured for Lock traps may contain negative depth

The problem: Method trace captured for Lock traps may contain negative depth. When we drill-down into the method trace in Trap Action History for Lock traps, the method trace may show -1 for the depth.

The reason: For Lock-based traps, method trace is captured before the transaction is over so the request stacks of those transactions is incomplete. This makes calculating the depth for partial events (a start without an end event) impossible.


Method trace unavailable or partially available

The problem: When using MOD L3, method trace data is either not found or was partially captured in Trap Action History, Server Activity Display, or Performance Analysis Report pages. This is due to having large number of method records associated with each monitored request. By default, the limit is 10000 method records. If the limit is exceeded, the method records will be discarded and will not be stored in the database.

The solution: Increase the Maximum Method Records value in System Properties by clicking Administration > Managing Server > System Properties.


Parent topic:

Run the Managing Server

+

Search Tips   |   Advanced Search