Kbase 33296: Operations with SERVER-SOCKET may result in Fatal transport failure -22 (5487)
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
Solution ID: P3296
FACT(s) (Environment):
Progress 9.1B
Progress 9.1C
Windows 32 Intel
SYMPTOM(s):
Fatal transport failure -22. (5487)
Fatal transport failure <error_code>. (5487)
4GL socket programing: Operations with SERVER-SOCKET
CAUSE:
Bug# 20001024-003
CAUSE:
There have been a few problems with the TCP/IP stack on Windows that required extra care to handle the WSAEWOULDBLOCK error.
FIX:
Add "READKEY PAUSE 0." after the "hSocket:DISCONNECT()." in the procedure(s) that manage the DISCONNECT().
The point of this fix is to slightly slow down the process. Using "PAUSE 1 NO-MESSAGE" or "PROCESS EVENTS" instead, does not solve the problem.
note: The fix, READKEY PAUSE 0, is not applicable if the code is running on an AppServer or in batch mode with -b. It will lead to:
** Attempt to read with no current source of input. (513)