Kbase P18702: Messenger corrupted in memory causing error Disconnecting - failed to receive header for the WEB_CGI
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
9/8/2008 |
|
Status: Verified
SYMPTOM(s):
Error received when accessing WebSpeed URL
Msngr: Disconnecting - failed to receive header for the WEB_CGIIP_GET_PROG message. (5806)
Disconnecting - failed to receive header for the WEB_CGIIP_GET_PROG message. (5806): Error -3
Msngr: Failure sending WEB_CGIIP_GET_PROG message. (5805)
Msngr: Failure sending WEB_CGIIP_GET_PROG message. (5805): Error -3
FACT(s) (Environment):
WebSpeed 3.1D
IIS 4.0
Windows NT 4.0
Database, WebSpeed broker and web server are on the same machine
wsasp.dll messenger is used
CAUSE:
The actual cause is unknown. Somehow the messenger is being corrupted in the memory. Microsoft has product called Microsoft Transaction Server (MTS) that can be used with IIS 4.0 or 5.0 to make the processes run in a separate memory spaces. This will allow the messenger to run each request in a separate memory space. Creating a package in MTS and add the wsasp.dll messenger component to the package will allow one to set a time in minutes to keep the messenger in the memory for a length of time. The default time is set to 5 minutes. If there is no IIS activity for 5 minutes, the messenger will be released from the memory and upon the web request, the messenger will be reloaded into the memory. Refer to the following URL link to read about MTS:
http://msdn.microsoft.com/library/default.asp?url=/archive/en-us/dnarmts/html/msdn_mtsintro.asp
FIX:
Add the wsasp.dll messenger component to an empty package in the Microsoft Transaction Server.
The following link shows how to create an empty package in MTS and add a component to the package:
http://msdn.microsoft.com/library/default.asp?url=/archive/en-us/dnarmts/html/msdn_mtsintro.asp