[Info-vax] Another "automatic update"

[Arne Vajhøj]

On 3/27/2019 12:03 PM, Dave Froble wrote:
> The task uses a third party toolset for socket communications.  From the 
> vendor:
> 
> This isn't something we've had reported by anyone else, but the error 
> itself is something that's reported back to us from the TCP/IP stack and 
> we propagate it back up to your application.
> 
> Best guess, something in the TCP/IP stack had a problem.  Not saying 
> it's impossible, but I don't see how the application program could have 
> caused it.

Based on what you tell us then there are two possibilities:
* MS broke something in the patch that were documented to work
* That third party library was doing something that was not documented
   to work but just accidentally worked until MS changed some internal
   behavior in the patch

It seems obvious that not everything TCP/IP was broken in Windows 2012.
That would have caused some headlines.

I do not completely understand your description:

#Turns out it's an error from WEENDOZE TCP/IP, where it attempts to
#connect to another connection request while the listener is currently
#attached to another connection.

But it sound like a somewhat unusual thing.

Maybe MS just missed it in their test.

Or they did test it but did not get hit by it:

#and of course, it's not a consistent error, just intermittent.

Their test system is different from your system and could
potentially have much longer intervals between the
error arising.

Bugs can be tricky.

Arne