Kbase P14941: WebSpeed agents hang in the BUSY state - looking for a cause
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/10/2008 |
|
Status: Verified
FACT(s) (Environment):
WebSpeed 3.1x
SYMPTOM(s):
WebSpeed agents hang in the BUSY state
Investigation of the WebSpeed server log file shows that the agent always execute the same procedure prior to end up in the BUSY state
CAUSE:
Application coding issue.
FIX:
Change the web/objects/web-disp.p procedure and add two messages: one before the "RUN run-web-object" marking the request started and one before the web-stream is closed marking the request end.
Locate the event:
ON "WEB-NOTIFY":U ANYWHERE DO:
and then make the modification:
...
MESSAGE "Request started for: " AppProgram . /*added */
RUN run-web-object IN web-utilities-hdl (AppProgram) NO-ERROR.
...
MESSAGE "Request ended for: " AppProgram . /* added */
OUTPUT {&WEBSTREAM} CLOSE.
Make sure that WebSpeed agent executes modified web-disp.p by putting it's location in the beginning of the PROPATH and compiling it as described in
P13578, What debugging code can be added to web-disp.p file to help troubleshoot WebSpeed agent hang issue
Set the server's logging level to 'Verbose'.
Run the application and after the problem presents itself, then investigate the server log file and locate the last procedure executed by the BUSY server process. Further investigation of the code should reveal the cause for the problem.