RFR: JDK-8317603: provide handleSocketErrorWithMessage in windows Net.c for extended exception messages [v4]

[Matthias Baesken]

> On Windows, we miss a handleSocketErrorWithMessage function that provides an additional message showing what went wrong in the Net.c coding.  On Unix we have this function. 
> This leads sometimes to exceptions like
> 
> MSG RTE: javax.naming.CommunicationException: example.com:1234 [Root exception is java.net.ConnectException: Connection timed out: no further information]
> 
> see https://bugs.openjdk.org/browse/JDK-8317307
> 
> It would be better to have a message explaining the reason instead of "no further information" .

Matthias Baesken has updated the pull request incrementally with one additional commit since the last revision:

  replace windows handleSocketError

-------------

Changes:
  - all: https://git.openjdk.org/jdk/pull/16057/files
  - new: https://git.openjdk.org/jdk/pull/16057/files/c3b7e85d..d5137560

Webrevs:
 - full: https://webrevs.openjdk.org/?repo=jdk&pr=16057&range=03
 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=16057&range=02-03

  Stats: 27 lines in 5 files changed: 9 ins; 8 del; 10 mod
  Patch: https://git.openjdk.org/jdk/pull/16057.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/16057/head:pull/16057

PR: https://git.openjdk.org/jdk/pull/16057