Kbase 21131: How To Interpret The Output of The Asbman Query Command
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
14/02/2011 |
|
Status: Verified
GOAL:
How To Interpret The Output of The Asbman Query Command
GOAL:
What information is returned by ASBMAN -query?
FACT(s) (Environment):
Progress 9.x
All Supported Operating Systems
OpenEdge 10.x
FIX:
Interpreting the output of the asbman "query" command involves
understanding the values in the nRq, nRcvd and nSent columns.
-- Online Help is brief
Progress Explorer online help currently gives only these simple, one-line descriptions:
nRq -- The number of messages sent by the server process.
nRcvd -- The number of messages received by the server process.
nSent -- The number of requests sent to the server process.
In the help documentation, the explanation for nRq and nSent are furthermore reversed, adding some confusion. The nRq and nSent definitions should read:
nRq - The number of requests sent to the server process.
nSent - The number of messages sent by the server process.]
-- Interpreting nRq, nRcvd, and nSent
The interpretation of these statistics varies depending on the
operating mode of the broker.
a) For State-aware and State-reset AppServers, the number of requests
represents the number of connections made from the client to the
AppServer. After the connection, all traffic takes place
directly between the client and the AppServer -- the broker is
not involved, so it does not keep any statistics on requests
or messages.
b) For State-aware/reset, the number of connections, the number of
requests, and the number of messages will always be the same.
That's because each connection only involves one message in each
direction.
c) For Stateless AppServer mode, the broker handles all traffic
between the client and the AppServer, so it can keep more
detailed statistics. In this context, the following operations
count as a request:
-- the "connect()" to the AppServer
-- each "run()"
-- the "disconnect()"
Each request can involve one or more request messages sent from
the client to the server (via the broker), followed by one or
more response messages sent from the server to the client
(again, via the broker).
The relative numbers seen in the nSent and nRcvd columns, as compared to those in the nRq column, is strictly application and data dependent. If the application generally sends small requests (under 8Kb) and small responses, then nRq, nRcvd, and nSent will all be fairly close. If the application transfers a lot of temp tables however, the numbers will differ more widely since each temp table is transferred as a series of 8Kb packets.
For WebSpeed, each web request involves sending a single message from the client to the broker, so the values of nRq and nRcvd will always be equal. The WebSpeed Broker does not handle any of the responses to the web requests, so the nSent value will also be the same as nRq and nRcvd.