Kbase 19086: Debugging methods on why Agents are not returning HTML pages
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
30/06/2005 |
|
Status: Verified
FACT(s) (Environment):
WebSpeed 3.x
SYMPTOM(s):
WebSpeed agent does not return an HTML page
Getting error 6383
WebSpeed Agent Error: Agent did not return an HTML page (6383)
CAUSE:
This error is generated by the WebSpeed Messenger when an Agent does not return output. When the messenger is waiting for output from an Agent, it checks the output for an "end of page" string, which indicates the agent has finished processing. This "end of page" message is generated by the Agent. If the Messenger receives this "end of page" message without actually receiving output from the client, error (6383) will occur.
Reasons to why no output was received can be related to the agent terminating abnormally, (i.e., GPF or memory violation) or a runtime error occurring within the program.
Examples of runtime errors are;
a. An agent may try to run some r-code that requires a particular database connection, but the agent is not connected to this database.
b. A program may try to find a record without a NO-ERROR, and the record is not found.
c. The CRCs in the r-code are not the same as CRCs in the database, and the program fails.
FIX:
Suggestions on debugging this problem
1. Always look at the WebSpeed log files for messages. Messages should be sent to these files if runtime errors occur.
2. Remove the -weblogerror parameter from the agent startup parameters, so that error messages are sent to the page, rather than being sent to the log files.
3. Put diagnostic messages throughout the code. Putting in diagnostics means that there is output from the agent, and can indicate where the program is failing. Make sure you put out some HTTP headers right at the start, or your browser may not be able to interpret what it was being sent. If you can isolate a program that is getting this error, try recompiling.
4. If using CGI messenger, check the timeout setting for your Webserver. If the procedure the agent is running exceeds the timeout before returning any information, the Webserver will destroy the CGI process and Progress will issue the 6383 error message.