IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1
Significant CPU consumption and high latency observed if a thread dump is requested
The problem: Significant CPU consumption by both the data collector and the Managing Server is observed if a thread dump is requested, and high latency is received in generating traps if thread dumps are requested when the trap is requested.
The solution: In a production environment, generating a thread dump is not encouraged as a trap action, due to the latency it will impose on trap actions and the high CPU time it will consume on the data collector and the Managing Server.
Performing a thread dump may also mean that you cannot access the application when you refresh the thread dump page.
Parent topic:
All platforms
Parent topic:
Run the Managing Server