Trapping error messages

Ian Andrews

New Member
We keep getting the error below, anyone any ideas as to help to trap this error, and what does in mean please.

WebSpeed error from WebSpeed NSAPI Messenger (WSNSA)

Msngr: Disconnecting with no header on WTA output web stream. (5814)
Msngr: other unclassified npp error. (6420)
error code is -1 , ID of the messenger sender is 784


------------------
 

Chris Kelleher

Administrator
Staff member
Ian-

Here is what the Progress KB has to say about the error:

<BLOCKQUOTE><font size="1" face="Arial, Verdana">quote:</font><HR>
When the browser sends a request for a WebSpeed page, the request is
passed from the web server to the messenger. The messenger contacts
the WebSpeed broker for a WebSpeed agent to handle the request. The
messenger then tries to contact this agent. A TCP socket is
established between the messenger and the agent, and the messenger
passes information to the agent.

At this point, the messenger is waiting for the agent to respond to
the request. When the agent responds, it should send a header
message first. If, for some reason, the connection between the agent
and the messenger is broken before this header message is sent, the
(5814) error will be generated by the messenger, and sent back to
the browser.

The (5814) error happens when the connection is broken without the
proper disconnect messages being passed between the messenger and
agent. If the agent is responding to a disconnect caused by the
program (e.g. QUIT), it will disconnect from the agent gracefully,
and will generate a different message.

The broken connection is usually caused either by some network error,
or by the agent dying for some reason before it can start fulfilling
the request.

This issue might be quite complicated to debug. Try the following
suggestions:
<UL TYPE=SQUARE>
<LI>check the status of the agents, see if there are any dead agents
(or if they are indeed starting), or for agents in LIMBO status.
<LI>put some code into $DLC/src/web/objects/web-disp.p to output a
"Content-type:" header first, so that any error messages that are
generated by a dying agent are written to the browser.
<LI>try running the code from a Progress client, to see if it
generates an error
<LI>try recompiling the program that you were trying to run.
</UL>
<HR></BLOCKQUOTE>

For more details, take a look at: http://www.progress.com/services/support/cgi-bin/techweb-kbase.cgi/kbase3.w?Sol_Id=18466

HTH.

-Chris

------------------
Chris Schreiber
ProgressTalk.com Manager
chris@fast4gl.com
 
Top