Re: Opening status – WSAEWOULDBLOCK/WSAEINVAL

[Traci Zee]

Rick,

This is just a guess.  When you stop the process the OS properly disconnects the tcp/ip connection so when you restart it comes back up.  When you stop the thread, the connection sometimes drops completely and sometimes doesn’t.

For my systems which are mostly UNIX, when tcp/ip over VPN fails there is a timeout issue.  Trouble is that there’s timeouts all over the place.

One of each of these for the Sending and Receiving systems.

1.  VPN timeout

2.  Firewall timeout

3.  OS TCP/IP timeout  <<< at least on Unix I've had to adjust this. 4.  Application TCP/IP timeout Any timeouts that occur for 1, 2, or 3 may cause odd status/connectivity in 4.  I make sure these are all longer than the Cloverleaf timeouts.  1 & 2 can have ‘inactivity’ timeouts. So, to conquer this problem, start asking about timeouts, inactivity timeouts, and are there any other timeouts from your network, firewall, and systems engineers.  There may be more than one firewall device that may need to be changed and they forgot it was in the loop.   A sniffer on the network goes a long way to telling you who isn’t playing by TCP/IPs rules. Traci Zee Emdeon