IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

Scenario 6: Determine the cause of connection problems

Annette, the level 2 operator, receives notification that the WASJ2CCPAvgWaitTimeHigh situation triggered. This error is critical. This situation indicates that the average wait time until a connection is granted is longer than 2 seconds.

  1. Annette navigates to the J2C Connections Pools workspace. This workspace reports information about resource adapters and connectors that adhere to J2EE Connector Architecture (J2C). J2C is the WAS implementation of the Java EE Connector Architecture (JCA). Data counters for this category contain usage information about the J2C connection pools that enable enterprise beans to connect to, and interact with, Enterprise Information Systems.

  2. In this workspace Annette observes in the Worst Wait Times view that some wait times for connections are above 2 seconds. The Highest Average Pool Sizes bar chart shows the largest average number of managed connections for each J2C connection pool. Typically, a connection takes no longer than 2 seconds.

  3. Annette uses an external ticketing tool to forward the ticket with details to Jim, the Middleware/Application Support SME.

  4. Jim navigates to the J2C Connections Pools workspace and compares the average pools size with the maximum pool size to establish the ideal maximum value. Jim establishes that the connection pool size needs to be adjusted, which is outside the scope of ITCAM for Application Diagnostics.


Parent topic:

Scenarios