Summary: | dev-java/icedtea-web-1.8.8-r1 Read Error: Could not read or parse the JNLP file | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | aditsu <aditsu> |
Component: | Current packages | Assignee: | Java team <java> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | aditsu |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://www.topcoder.com/contest/arena/ContestAppletProd.jnlp | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | javaws output |
Description
aditsu
2024-01-26 12:08:27 UTC
Created attachment 883165 [details]
javaws output
Root cause may be this (from the output): java.net.SocketException: Connection refused (Connection refused) But I have no idea why it fails to connect. I just noticed now: at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:435) SocksSocket??? Is it trying to use a SOCKS proxy? I have a SOCKS proxy set in firefox, but nowhere else. It's not even my main browser, and I'm not using it at the moment. Is java/icedtea-web blindly following the proxy settings from firefox?! That would be HORRIBLY wrong. Finally I discovered that icedtea-web has an itweb-settings command for configuration. In the network section it was set to use browser settings. It makes absolutely NO SENSE that it took the settings from firefox rather than chromium (which is my default browser). Anyway, after changing to "direct connection", the application is loading. So there are 2 problems here: 1. icedtea-web is following the proxy settings from the WRONG browser 2. When it fails to connect, it doesn't provide a clear explanation |