Measures reported by PepAppQueueTest

When a Tuxedo application server process carries out a request, it makes a call to a service, such as MgrGetObject. The server process waits for the service to complete, then returns information to the device that initiated the request, such as a browser. While a server process waits for a service to complete, other transaction requests wait in a queue until the current service completes. A service may take a fraction of a second to complete or several seconds, depending on the type and complexity of the service. When the service completes, the server process is then available to process the next request in the corresponding queue.

If the length of a queue keeps increasing, it is a sign that the corresponding server process is unable to process requests quickly. Therefore, to be able to swiftly spot a probable processing bottleneck in an application server domain, administrators must monitor the queues in the domain continuously, isolate those queues that are growing in length, and identify which server process is using that queue. This can be achieved using the PepAppQueueTest.

This test auto-discovers the queues used by each server process in a domain, and for every queue, reports the number of requests in the queue and the number of instances of that server process sharing the queue. This way, the test rapidly leads administrators to a potential slowdown in request processing by a domain, and helps them accurately isolate which server process is contributing to the slowdown.

The measures made by this test are as follows: