-
Bug
-
Resolution: Cannot Reproduce
-
P3
-
None
-
6
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2143097 | Thomas Ng | P3 | Closed | Won't Fix |
jdk build b91 --> b92 regression, detected on Solaris and Linux.
JavaWS does not resolve host's local name returned by java.net.InetAddress.getHostName().
E.g. attempt to start "myapp.jnlp" from "myhost" on the same host
javaws http://myhost/myapp.jnlp
fails with
CouldNotLoadArgumentException[ Could not load file/URL specified: ... ]
the nested IOException contains confusing message:
Server returned HTTP response code: 500 for URL: ...
That is not true: the HTTP server did not return that status code, because it did not recieve an HTTP request at all.
This issue raised if host's local names are presented in URLs from a jnlp file also.
(Please find actual stack traces for both the exceptions in Comments section)
Resolution for canonical fully-qualified host name or IP address works OK.
JavaWS does not resolve host's local name returned by java.net.InetAddress.getHostName().
E.g. attempt to start "myapp.jnlp" from "myhost" on the same host
javaws http://myhost/myapp.jnlp
fails with
CouldNotLoadArgumentException[ Could not load file/URL specified: ... ]
the nested IOException contains confusing message:
Server returned HTTP response code: 500 for URL: ...
That is not true: the HTTP server did not return that status code, because it did not recieve an HTTP request at all.
This issue raised if host's local names are presented in URLs from a jnlp file also.
(Please find actual stack traces for both the exceptions in Comments section)
Resolution for canonical fully-qualified host name or IP address works OK.
- backported by
-
JDK-2143097 solaris/linux: Javaws does not recognize the "default" browser
- Closed
- duplicates
-
JDK-6478792 JavaWS does not allow JNLP app to connect to another port at the same host
- Closed