IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1
Method report does not contain the expected trace although MOD-L3 and proper filter definition are specified
The problem: Despite using a monitoring level of MOD-L3 and having a proper filter definition specified in the method_entry_exit.xml file, the method report does not contain the expected trace.
The cause: If you are missing methods in a trace, and have checked that there are no dropped records, then the most likely cause is the incorrect use of exclude overrides.
The solution: Carry out the following steps:
- Optional step. Create a new configuration with the appropriate exclude list if you need to trace the WAS system classes. Otherwise you can use the standard J2EE configuration (default).
- Switch to MOD-L3.
- Close WAS (stop data collector).
- Create method_entry_exit_customer-name.xml, copying your filter definition.
- Point to this file in toolkit_custom.properties in the <DC>/runtime/<server>/custom directory (with the collect method entry exit parameter set to true)
Do not update toolkit.custom.properties in the <DC>/itcamdc/etc directory. User modifications must always be made to the <DC>/runtime/<server>/custom directory.
- Even if it is not necessary to delete the toolkit and classinfo files from the <DC>/runtime/<server> directory, you can remove them anyway, as they are system-generated files:
<nodename>.<was-name>.toolkit.properties.xml
<nodename>.<was-name>.toolkit.xml
<nodename>.<was-name>.classinfo.txt
- Start WAS (start data collector ).
- Run a customer application.
- Collect L3 trace.
- Optional step. Switch to L2 and collect some "Misbehaving Transaction" traps.
Check in PAR Reports or Trap History Reports for the expected data.
Parent topic:
All platforms