RFR [13] 8229018: Switching to an infinite socket timeout on Windows leads to high CPU load

[Michael McMahon]

Could we get the following change (from Alan Bateman) reviewed please?

http://cr.openjdk.java.net/~michaelm/8229018/webrev.1/index.html

It is a long standing issue but was only uncovered after switching the 
classic
networking socket impl to use NIO in JDK 13. The bug is seen when 
setting a finite timeout
on a socket and then switching back to block forever, which results in a 
busy loop.

There is no regression test as it is difficult to test this kind of 
issue which
only results in CPU overhead.

Thanks,
Michael