JDK-8166747 : Add invalid network / computer name cases to isReachable known failure switch
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.net
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows
  • Submitted: 2016-09-26
  • Updated: 2022-06-27
  • Resolved: 2016-09-27
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
7u281Fixed 8u152Fixed 9 b138Fixed
Related Reports
Relates :  
In the ping4() call in Inet4AddressImpl.c on Windows there is a switch statement containing failure codes for IcmpSendEcho which correspond to well known and expected failures for this call when a host is not reachable. In these cases ping4() simply returns false as opposed to throwing an exception.

Prior releases of the JDK would return false when using the tcp ping method where we currently throw an exception with the ERROR_INVALID_COMPUTERNAME (Windows error code 1210) or ERROR_INVALID_NETNAME (1214) errors. We should add these cases to the switch statement for compatibility purposes.
URL: http://hg.openjdk.java.net/jdk9/jdk9/jdk/rev/665096863382 User: lana Date: 2016-09-28 20:43:19 +0000

URL: http://hg.openjdk.java.net/jdk9/dev/jdk/rev/665096863382 User: robm Date: 2016-09-27 11:08:03 +0000