-
Bug
-
Resolution: Other
-
P3
-
8u161
-
x86_64
-
other
FULL PRODUCT VERSION :
java version "1.8.0_161"
Java(TM) SE Runtime Environment (build 1.8.0_161-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.161-b12, mixed mode)
ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows [Version 10.0.16299.192]
A DESCRIPTION OF THE PROBLEM :
Using an IPv6 address URL in JNLP file in codebase attribute, application is not starting, java launcher hangs (32 bit) or terminates (64 bit).
If I change the codebase value to an hostname or IP v4 address manually, same file is starting.
Not working:
<jnlp spec="6.0+" codebase="http://[fe80::xxxxxxxx]/" ....
Same with official addresses, not only a link local address problem.
Same file with IPv6 address used with Java 8U151 is working.
REGRESSION. Last worked in version 8u151
ADDITIONAL REGRESSION INFORMATION:
java version "1.8.0_152"
Java(TM) SE Runtime Environment (build 1.8.0_152-b16)
Java HotSpot(TM) 64-Bit Server VM (build 25.152-b16, mixed mode)
REPRODUCIBILITY :
This bug can be reproduced always.
java version "1.8.0_161"
Java(TM) SE Runtime Environment (build 1.8.0_161-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.161-b12, mixed mode)
ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows [Version 10.0.16299.192]
A DESCRIPTION OF THE PROBLEM :
Using an IPv6 address URL in JNLP file in codebase attribute, application is not starting, java launcher hangs (32 bit) or terminates (64 bit).
If I change the codebase value to an hostname or IP v4 address manually, same file is starting.
Not working:
<jnlp spec="6.0+" codebase="http://[fe80::xxxxxxxx]/" ....
Same with official addresses, not only a link local address problem.
Same file with IPv6 address used with Java 8U151 is working.
REGRESSION. Last worked in version 8u151
ADDITIONAL REGRESSION INFORMATION:
java version "1.8.0_152"
Java(TM) SE Runtime Environment (build 1.8.0_152-b16)
Java HotSpot(TM) 64-Bit Server VM (build 25.152-b16, mixed mode)
REPRODUCIBILITY :
This bug can be reproduced always.