JDK-8220499 : Update JDK networking tests for IPv6-only environments
  • Type: Enhancement
  • Component: core-libs
  • Sub-Component: java.net
  • Affected Version: 13
  • Priority: P3
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2019-03-12
  • Updated: 2022-01-17
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.
Other
tbdUnresolved
Related Reports
Relates :  
JDK-8280091 - Bypass execution of tests with -Djava.net.preferIPv4Stack=true property setting in IPv6 only environment
Relates :  
JDK-8280099 - sun/net/www/protocol/http/TunnelThroughProxy.java fails with timeout
Relates :  
JDK-8221681 - Improved IPv6 Support
Relates :  
JDK-8184770 - JDWP support for IPv6
Relates :  
JDK-8280104 - sun/net/www/protocol/https/HttpsClient/ProxyAuthTest.java fails with test timeout
Sub Tasks
JDK-8220083 :  
Remove hard-coded 127.0.0.1 loopback address in JDK networking tests - Resolved
JDK-8220575 :  
Correctly format test URI's that contain a retrieved IPv6 address - Resolved
JDK-8220673 :  
Add test library support for determining platform IP support - Resolved
JDK-8220675 :  
Investigate IPv6-only build or LD_PRELOAD - Open
JDK-8221570 :  
Update hardcoded 127.0.0.1 in tests that use pre-generated certificates. - Open
JDK-8221684 :  
Correctly format test URI's that contain an IPv6 address retrieved from the host - Open
JDK-8223652 :  
Rename IPSupport.skipIfCurrentConfigurationIsInvalid() - Resolved
JDK-8223880 :  
Update sun/net/ftp/FtpURL.java and sun/net/ftp/FtpURLConnectionLeak.java to work with IPv6 addresses - Resolved
JDK-8224014 :  
Don't run test/jdk/java/net/NetworkInterface/IPv4Only.java in IPv6 only environment - Resolved
JDK-8224018 :  
test/jdk/java/net/ipv6tests/{Tcp,Udp}Test.java assume IPv4 is available - Resolved
JDK-8224019 :  
test/jdk/java/nio/channels/DatagramChannel/BasicMulticastTests.java assumes IPv4 is always available - Resolved
JDK-8224081 :  
SOCKS v4 tests require IPv4 - Resolved
JDK-8224248 :  
test/jdk/java/net/InetAddress/CheckJNI.java assumes 127.0.0.1 is available - Resolved
JDK-8224256 :  
test/jdk/java/security/SecureClassLoader/DefineClass.java hardcodes 127.0.0.1 - Resolved
Description
Many of the networking tests in the JDK assume IPv4 support. This may not always be the case.

Specifically:
 1) Remove hardcoded IPv4 literals, e.g. 127.0.0.1.
 2) Correctly format URI's that contain a retrieved IPv6 literal host, e.g. add square brackets.
 3) Update hardcoded 127.0.0.1 in tests that use pre-generated certificates.
 4) Optional-ize tests that run with -Djava.net.preferIPv4Stack
 5) Ensure use of preferIPv6Addresses, where applicable
 6) ...

A test library utility that correctly determines the environment would be useful, e.g. IPv4-only, IPv4/IPv6 ( dual stack ), or IPv6-only.
Comments
I see Chris has already linked JDK-8184770 to JDK-8221681, the umbrella bug for implementation issues. Thanks!
01-04-2019
The JDK-8184770 work is related to this well.
29-03-2019