Kbase P75943: Can I know agent processing statistics by looking at output from wtbman -q?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
26/10/2010 |
|
Status: Verified
GOAL:
Can I get agent processing statistics by looking at output from wtbman -q?
GOAL:
Agents being killed after being busy for 10 minutes, but wtbman -q shows Request Duration average is zero, why?
GOAL:
What is Rq Duration (max, average) in wtbman -q output?
FACT(s) (Environment):
All Supported Operating Systems
WebSpeed 3.x
OpenEdge 10.x
FIX:
Rq Duration (max, average) - The maximum and average duration of requests
processed by the broker.
The duration starts when the broker receives the request for an agent port
number, and ends when the broker transmits the port number back to the
messenger. It really measures how long the broker took to process the request.
It does not include the time for the messenger to look up the broker via the
NameServer, create the TCP/IP connection to the broker, send the port request,
receive the port response, disconnect from the broker, reconnect to the agent, etc.
The Rq Duration time does NOT include the time to actually run the request in the agent ...
The processing of a web request goes like following:
1. Web server / messenger receives a request from browser
2. Messenger connects and looks up name server for the broker service info
3. After obtaining service / broker information, the messenger connects to
the broker via tcp/ip and request agent to process the request
4. Broker receives the request and locates an available agent from agent pool
5. Broker sends agent port to the messenger
6. Messenger connects to agent
7. Agent processes request
8. Agent sends results back to the messenger
The request duration actually is for steps 4 and 5, but the agent processing time is in step 7.
In addition, the more agents become busy, the less available agents in the agent pool,
the more time it will take broker to locate an available agent.
The wtbman command shows broker timing statistics but not for the agents.
In order to know what each agent is processing and for how long, server logging has to be turned on
to show more information. In Webspeed 3.1D, 4GL tracing can also assist in debugging busy agent issue.