Kbase P126664: Why doesn't verbose broker logging report any new client requests from WSASP and WSISA messenger?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/30/2007 |
|
Status: Unverified
GOAL:
Why doesn't verbose broker logging report any new client requests from WSASP and WSISA messenger?
GOAL:
How to get client requests from WSASP and WSISA messenger logged in broker log file?
GOAL:
Which broker logging level will log client's requests from WSASP and WSISA messengers?
FIX:
At verbose logging level, what the broker is actually logging are connections made from the messenger for agent port numbers. For cgiip,every request must make a connection to the broker to request the port
number. This is because a new instance of cgiip is launched for each request.
However, isapi and nsapi messengers are persistent in the webserver; once loaded they remain resident. Therefore, we create a single, persistent connection to the broker that is used for all port requests.
Since we are not making new connections for each request, nothing extra is logged at the verbose level.
For Progress V9, following logging level can be set to generate extra logging for the requests
brkrLoggingLevel to log
---------------- ------
68 client FSM
516 client msgs (log complete msg)
772 terse client msgs (log only first 64 bytes of msg)
For OE, start by setting broker logging level to 4, then add different logEntryTypes.