Kbase P3296: Operations with SERVER-SOCKET may result in Fatal transport failure -22 (5487)
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
29/05/2009 |
|
Status: Verified
SYMPTOM(s):
Fatal transport failure -22. (5487)
Fatal transport failure <error_code>. (5487)
4GL socket programing: Operations with SERVER-SOCKET
FACT(s) (Environment):
Progress 9.1B
Progress 9.1C
Windows 32 Intel
OpenEdge Category: Language (4GL/ABL)
CAUSE:
Bug# OE00062025
CAUSE:
There have been a few problems with the TCP/IP stack on Windows that required extra care to handle the WSAEWOULDBLOCK error. One problem was when we get the CONNECT event, there is no guarantee that any bytes are available on the socket at that moment. We only guarantee that there is a socket to use.
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.