-
Bug
-
Resolution: Duplicate
-
P1
-
None
-
6
-
generic
-
generic
jdk build b91 --> b92 regression, detected on Solaris and Linux.
If an JNLP application tries to establish a socket connection to another port at its "native" host, SocketException is thrown with the following message:
java.net.SocketException: SOCKS: Connection not allowed by ruleset
For example, the problem appears if the application http://myhost.sun.com:8080/myapp.jnlp tries to establish a socket connection with http://myhost.sun.com:8081
(Please find actual stack trace in Comments section)
This issue impacts all existing JNLP TCK tests, because the tests use socket connections to report results to JavaTest harness. This is an important part of the TCK architecture.
If an JNLP application tries to establish a socket connection to another port at its "native" host, SocketException is thrown with the following message:
java.net.SocketException: SOCKS: Connection not allowed by ruleset
For example, the problem appears if the application http://myhost.sun.com:8080/myapp.jnlp tries to establish a socket connection with http://myhost.sun.com:8081
(Please find actual stack trace in Comments section)
This issue impacts all existing JNLP TCK tests, because the tests use socket connections to report results to JavaTest harness. This is an important part of the TCK architecture.
- duplicates
-
JDK-6478804 solaris/linux: Javaws does not recognize the "default" browser
- Closed