Opened 9 years ago
Last modified 8 years ago
#12096 new defect
Getting "Read timed out" when trying to download a layer
Reported by: | Owned by: | team | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | tested |
Keywords: | read_timed_out, error | Cc: |
Description
What steps will reproduce the problem?
- Try downloading a random map layer different from the default Mapnik layers
- Read error "Read timed out" and hit OK
- Try step 1 and 2 again for 20 times and eventually give up
What is the expected result?
It should load the map layer, but sadly this isn't happening. Restarting PC, reinstalling software and restart program doesn't work.
What happens instead?
Nothing happens and an error "Read timed out" appears. Which is weird, because I also still have JOSM version 8491 on my machine. This version takes a little longer to load, but after a minute eventually loads my layer! While JOSM 8969 loads for like 20 seconds and gives an error all the time.
Please provide any additional information below. Attach a screenshot if possible.
I suspect this might have something to do with the loading. Why would the old version work and the new version not? Had this problem too with the version before 8969, actually since the "new" JOSM with the new initialisation screen.
Tho I'm still using v. 8491 to get the work done. Some plug-ins may not work, but at least it loads my map layers correctly
Revision: 8969 Repository Root: http://josm.openstreetmap.de/svn Relative URL: ^/trunk Last Changed Author: Don-vip Last Changed Date: 2015-10-29 22:15:23 +0100 (Thu, 29 Oct 2015) Build-Date: 2015-10-30 02:32:24 URL: http://josm.openstreetmap.de/svn/trunk Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Last Changed Rev: 8969 Identification: JOSM/1.5 (8969 nl) Windows 8 64-Bit Memory Usage: 100 MB / 247 MB (39 MB allocated, but free) Java version: 1.8.0_51, Oracle Corporation, Java HotSpot(TM) Client VM VM arguments: [-Djava.security.manager, -Djava.security.policy=file:C:\Program Files (x86)\Java\jre1.8.0_51\lib\security\javaws.policy, -DtrustProxy=true, -Djnlpx.home=<java.home>\bin, -Djnlpx.origFilenameArg=C:\Users\Patrick\AppData\LocalLow\Sun\Java\Deployment\cache\6.0\56\1ee8cfb8-52109141, -Djnlpx.remove=false, -Djava.util.Arrays.useLegacyMergeSort=true, -Djnlpx.splashport=50201, -Djnlp.application.href=https://josm.openstreetmap.de/download/josm.jnlp, -Djnlpx.jvm=<java.home>\bin\javaw.exe, -Djnlpx.vmargs=LURqYXZhLnV0aWwuQXJyYXlzLnVzZUxlZ2FjeU1lcmdlU29ydD10cnVlAC1Eam5scC5hcHBsaWNhdGlvbi5ocmVmPWh0dHBzOi8vam9zbS5vcGVuc3RyZWV0bWFwLmRlL2Rvd25sb2FkL2pvc20uam5scAA=] Plugins: - ElevationProfile (31694) - PicLayer (31694) - RoadSigns (31694) - log4j (31603) - measurement (31694) - reverter (31694) - turnlanes (31603) - turnrestrictions (31694) Last errors/warnings: - W: Cannot start IPv6 remotecontrol https server on port 8112: Address already in use: JVM_Bind - W: Cannot lock cache directory. Will not use disk cache - E: org.openstreetmap.josm.io.OsmTransferException: java.net.SocketTimeoutException: Read timed out. Oorzaak: java.net.SocketTimeoutException: Read timed out - E: org.openstreetmap.josm.io.OsmTransferException: java.net.SocketTimeoutException: Read timed out. Oorzaak: java.net.SocketTimeoutException: Read timed out - E: org.openstreetmap.josm.io.OsmTransferException: java.net.SocketTimeoutException: Read timed out. Oorzaak: java.net.SocketTimeoutException: Read timed out
Attachments (0)
Change History (5)
follow-up: 2 comment:1 by , 8 years ago
comment:3 by , 8 years ago
Replying to patrickmeijer95@…:
Which is weird, because I also still have JOSM version 8491 on my machine. This version takes a little longer to load, but after a minute eventually loads my layer! While JOSM 8969 loads for like 20 seconds and gives an error all the time.
Eventually, you might be able to narrow the gap of revisions. You'll find old versions in the Archiv.
I get the same problem downloading some changesets. For example try downloading changeset 42904744. I checked my network usage, and there is no data being transfered. I think it takes so long because it's so large and the server takes awhile to process it and JOSM times out before the server is ready with the data. Using this tool works alright, although takes awhile.