Opened 10 years ago
Closed 8 years ago
#11932 closed defect (worksforme)
Failing connections
| Reported by: | A_Pirard | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core | Version: | latest |
| Keywords: | Cc: |
Description
Hi,
Now at 8677 on Ubuntu 12.04, happened in previous versions.
Since some time, I occasionally get a message such as the following,
then I stop/restart JOSM and it runs just fine:
JOSM tried to access the following resources:
https://josm.openstreetmap.de/wiki/StartupPage
but failed to do so, because of the following network errors:
java.net.SocketTimeoutException: Read timed out
It may be due to a missing proxy configuration. Would you like to change your proxy settings now?
Recently, I got the following message twice
Failed to open a connection to the remote server 'https://api.openstreetmap.org/api/0.6/map?bbox=5.6596668,50.518239,5.6738692,50.524958'. Please check your internet connection.
That condition is "sticky". I have to stop/restart too to clear it.
"status" attached
My Internet connection exhibits no problems.
$ sudo ping -f josm.openstreetmap.de PING josm.openstreetmap.de (78.47.79.181) 56(84) bytes of data. --- josm.openstreetmap.de ping statistics --- 2285 packets transmitted, 2281 received, 0% packet loss, time 32103ms rtt min/avg/max/mdev = 43.532/53.212/205.559/23.067 ms, pipe 15, ipg/ewma 14.055/47.378 ms
$ sudo ping -f api.openstreetmap.org PING api.openstreetmap.org (193.63.75.100) 56(84) bytes of data. --- api.openstreetmap.org ping statistics --- 2417 packets transmitted, 2414 received, 0% packet loss, time 33799ms rtt min/avg/max/mdev = 43.756/46.265/64.259/2.375 ms, pipe 6, ipg/ewma 13.989/45.652 ms
Attachments (2)
Change History (7)
by , 10 years ago
| Attachment: | JOSMstatus.txt added |
|---|
comment:1 by , 10 years ago
comment:2 by , 10 years ago
Can you start JOSM in commandline and paste the output for cases where this happens.
comment:3 by , 10 years ago
OK, I changed my shortcut to launch terminal and I'll get back with news.
A hint maybe? (is IPV6 commonly used?)
INFO: Detected useable IPv6 network, prefering IPv6 over IPv4.
...
INFO: RemoteControl::Accepting remote connections on /127.0.0.1:8111
INFO: RemoteControl::Accepting remote connections on /0:0:0:0:0:0:0:1:8111
by , 10 years ago
| Attachment: | JOSM trace.txt added |
|---|
comment:4 by , 10 years ago
Here is one, containing a tcptraceroute showing that the server is reachable.
comment:5 by , 8 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
Never happened again with late JOSM versions and Ubuntu's OpenJDK Runtime Environment (build 1.8.0_45-internal-b14).



May I recall this problem?
I have now upgraded java to 8 and the problem remains.
openjdk version "1.8.0_45-internal"
OpenJDK Runtime Environment (build 1.8.0_45-internal-b14)
OpenJDK 64-Bit Server VM (build 25.45-b02, mixed mode)
It may occur when JOSM starts up or during a session, which is more annoying.
Or should I say it was because the new, WONDERFUL Save Session (THANS!!!) alleviates that.
Here is a typical log:
JOSM tried to access the following resources:
https://josm.openstreetmap.de/maps
https://josm.openstreetmap.de/wiki/StartupPage
but failed to do so, because of the following network errors:
java.net.ConnectException: Network is unreachable
It may be due to a missing proxy configuration. Would you like to change your proxy settings now?
Failed to open a connection to the remote server 'https://api.openstreetmap.org/api/0.6/map?bbox=5.5827981,50.5685605,5.5833989,50.5688672'. Please check your internet connection.
URL:http://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2015-11-24 00:04:12 +0100 (Tue, 24 Nov 2015)
Build-Date:2015-11-23 23:14:21
Revision:9060
Relative:URL: /trunk
Identification: JOSM/1.5 (9060 en) Linux Ubuntu 12.04 LTS
Memory Usage: 355 MB / 1266 MB (136 MB allocated, but free)
Java version: 1.8.0_45-internal, Oracle Corporation, OpenJDK 64-Bit Server VM
VM arguments: [-Djosm.restart=true, -Djava.net.useSystemProxies=true]