IBM Tivoli Composite Application Manager for Application Diagnostics, Version 188.8.131.52
Scenario 1: Detecting a memory leak
After creating a Memory Analysis report that compares JVM Heap Size to Average Response Time, you think there is a memory leak. Access the Memory Leak feature to see if the amount of uncollected memory is increasing. You set up a candidate for the server in question. This tells the system to collect heap data now and again after a specified amount of time. Then you can compare the heap data for the two periods of time to determine if there is evidence of a memory leak.
Scenario 2: Supporting your claim that the purchase of new servers is necessary
The year end budget is due and project whether you will need to buy more servers for your environment. You create a Memory Analysis report during peak usage and compare JVM Heap Size to the Number of Sessions. The number of servers is close to maxing out the current environment. As a capacity planner, you recommend that the company increase the number of servers currently servicing the environment.
Parent topic:Memory diagnosis