Kbase P48192: Errors using wsisa.dll without name server
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
09/11/2010 |
|
Status: Verified
SYMPTOM(s):
Errors using wsisa.dll without name server
Error 8558 and 8091 are in the WebSpeed broker log file
Errors 5805 and 6420 displayed in the browser
ERROR: connection refused : maximum number of client connections has been reached. (8558)
Error Maximum number of client connections has been reached. ... disconnecting client. (8091)
Msngr: Failure sending WEB_CGIIP_GET_PROG message. (5805)
Msngr: other unclassified npp error. (6420)
The following is displayed in the browser with ISAPI messenger: HTTP/1.1 500 Internal Server Error Server: Microsoft-IIS/5.0 Date: Tue, 14 Oct 2003 20:51:06 GMT X-Powered-By: ASP.NET Connection: close WebSpeed error from WebSpeed ISAPI Messenger(WSISA) Msngr: Failure sending WEB_CGIIP_GET_PROG message. (5805) Msngr: other unclassified npp error. (6420) error code is -1, Connection ID of the message sender is 0
wsisa.dll directly connects to webspeed broker, name server is not used
The problem not seen when name server is used
The problem not seen when the CGI messenger is used exclusively.
Error could also occur when both wsisa.dll and cgiip are in use.
If cgiip is also concurrently used, CGI (cgiip.exe) messenger displays the following error in the browser when error 8558 and 8091 are displayed in the broker log: WebSpeed error from messenger process (6019) Msngr: Disconnecting - all agents are currently busy, please try again later. (5832)
FACT(s) (Environment):
WebSpeed 3.1D
OpenEdge 10.0A
IIS 5.0
CAUSE:
Bug# OE00096137
CAUSE:
The ISAPI messenger is not releasing the client thread after the request is fulfilled by the Webspeed agent. When the maxClientInstance (max client thread count) reaches the number set in ubroker.properties file (default is 512), the broker is unable to serve more client requests. Hence, both messengers will display the errors as stated in the symptoms.
FIX:
Upgrade to Progress 9.1D08 or later
Upgrade to OpenEdge 10.0A01 or later
Upgrade to OpenEdge 10.0B or later
Possible workarounds:
- Do not bypass the NameServer when using wsisa.dll
- Use cgiip messenger instead of using wsisa.dll