non-blocking SocketChannel connect broken on Windows 8

[Alan Bateman]

Jeroen Frijters wrote:
> :
> It's definitely a behavior change in Windows 8 and I agree that it probably has some compatibility impact, but fundamentally I think that the OpenJDK code is wrong, unless there is documentation somewhere that claims that the socket will be bound when the async connect is initiated.
>   
We're assuming connect/getsockname work like they do on Unix/Linux so 
this isn't the first time we've been caught out by Windows differences.  
I'll create a bug for this as this will clearly break existing code.

-Alan.