Opened 3 years ago
Closed 3 years ago
#22052 closed defect (needinfo)
"Nominatim" search is inhibited from the 2nd launch of JOSM onwards
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core | Version: | latest |
| Keywords: | template_report, windows | Cc: |
Description
What steps will reproduce the problem?
- Install the latest build of JOSM for Windows (by josm-setup.exe) or any other Java 16-17 build from scratch, then launch it.
- Go to "Download map data from a server of your choice (Ctrl+Shift+Down) > Areas around places > Enter a place name to search for: > Search...". Initially, "Nominatim" search will work normally.
- Restart JOSM by closing and reopening it or by pressing "Ctrl+Alt+Shift+J".
- Repeat Step 2 then draw the conclusions.
What is the expected result?
"Nominatim" server should remain available even after the very first launch of JOSM.
What happens instead?
JOSM is no longer able to reach "Nominatim" server from its 2nd launch onwards. Search process stalls on "Querying name server..." for a couple of seconds and finally ends with the following message: "Failed to upload data to or download data from 'https://nominatim.openstreetmap.org/search?format=xml&q=' due to a problem with transferring data. Details (untranslated): Connect timed out".
Please provide any additional information below. Attach a screenshot if possible.
It basically happens with each Java 16-17 build of JOSM for Windows (18191 onwards). It works flawlessly on 1st launch of JOSM right after a fresh installation, but from the 2nd start onwards the "Nominatim" search will no longer work (except by uninstalling and reinstalling JOSM from scratch).
Revision:18427 Build-Date:2022-04-05 19:23:14 Identification: JOSM/1.5 (18427 en) Windows 10 64-Bit OS Build number: Windows 10 Pro 2009 (19044) Memory Usage: 320 MB / 4078 MB (155 MB allocated, but free) Java version: 17.0.2+8-LTS, Azul Systems, Inc., OpenJDK 64-Bit Server VM Look and Feel: com.sun.java.swing.plaf.windows.WindowsLookAndFeel Screen: \Display0 3840×2160 (scaling 1.50×1.50) Maximum Screen Size: 3840×2160 Best cursor sizes: 16×16→48×48, 32×32→48×48 System property file.encoding: Cp1252 System property sun.jnu.encoding: Cp1252 Locale info: en_IT Numbers with default locale: 1234567890 -> 1234567890 VM arguments: [-Djpackage.app-version=1.5.18427, --add-modules=java.scripting,java.sql,javafx.controls,javafx.media,javafx.swing,javafx.web, --add-exports=java.base/sun.security.action=ALL-UNNAMED, --add-exports=java.desktop/com.sun.imageio.plugins.jpeg=ALL-UNNAMED, --add-exports=java.desktop/com.sun.imageio.spi=ALL-UNNAMED, --add-opens=java.base/java.lang=ALL-UNNAMED, --add-opens=java.base/java.nio=ALL-UNNAMED, --add-opens=java.base/jdk.internal.loader=ALL-UNNAMED, --add-opens=java.base/jdk.internal.ref=ALL-UNNAMED, --add-opens=java.desktop/javax.imageio.spi=ALL-UNNAMED, --add-opens=java.desktop/javax.swing.text.html=ALL-UNNAMED, --add-opens=java.prefs/java.util.prefs=ALL-UNNAMED, -Djpackage.app-path=%UserProfile%\AppData\Local\JOSM\JOSM.exe] Last errors/warnings: - 00000.329 W: extended font config - overriding 'filename.Myanmar_Text=mmrtext.ttf' with 'MMRTEXT.TTF' - 00000.332 W: extended font config - overriding 'filename.Mongolian_Baiti=monbaiti.ttf' with 'MONBAITI.TTF' - 00002.335 E: java.security.KeyStoreException: Windows-ROOT not found. Cause: java.security.NoSuchAlgorithmException: Windows-ROOT KeyStore not available - 00033.471 W: java.net.SocketTimeoutException: Connect timed out - 00033.473 E: org.openstreetmap.josm.io.OsmTransferException: java.net.SocketTimeoutException: Connect timed out. Cause: java.net.SocketTimeoutException: Connect timed out - 00033.486 E: IO Exception - <html>Failed to upload data to or download data from<br>'https://nominatim.openstreetmap.org/search?format=xml&q=roma'<br>due to a problem with transferring data.<br>Details (untranslated): Connect timed out</html>
Attachments (1)
Change History (10)
by , 3 years ago
| Attachment: | josm-java1617-windows-nominatim-search-bug.jpg added |
|---|
comment:1 by , 3 years ago
| Keywords: | windows added |
|---|---|
| Priority: | major → normal |
comment:2 by , 3 years ago
I tried Nominatim search on build 18118 and it works as expected, so i guess not to be rate limited on Nominatim. The same applies on Firefox browser (https://nominatim.openstreetmap.org/ui/search.html?q=roma). I checked "socket.timeout.connect" value in Advanced Preferences and is always on 15.
comment:3 by , 3 years ago
Thanks for getting back on this.
Like I said, I don't have a windows machine, so this is (unfortunately) going to have to wait for a dev with a windows machine. I was really hoping it was one of the other potential problems.
comment:4 by , 3 years ago
I cannot reproduce on Winodws. I installed with latest josm-setup.exe and start JOSM with a double click on the icon JOSM. No problems with Nominatim after restart.
Edit: For a status report see #22053
follow-up: 6 comment:5 by , 3 years ago
@n34s: I'm now wondering if this is a configuration problem somewhere.
Can you do the following:
- JOSM Preferences ->
Advanced Preferences-> Search foroauth-> Selectoauth.access-token.keyandoauth.access-token.secret->Reset-- this will log you out of OSM. (I've got a patch somewhere that will remove the need to do this, but I don't think I've applied it yet) - Clear the search field (
oauth->) - Select everything (
ctrl+a) Export selected itemsMore...->Reset preferences
If that does not fix the problem, then you can reload your preferences from the file saved in step 4. If it does fix the problem, then it is a configuration setting somewhere.
comment:6 by , 3 years ago
<Replying to taylor.smock:
@n34s: I'm now wondering if this is a configuration problem somewhere.
Can you do the following:
- JOSM Preferences ->
Advanced Preferences-> Search foroauth-> Selectoauth.access-token.keyandoauth.access-token.secret->Reset-- this will log you out of OSM. (I've got a patch somewhere that will remove the need to do this, but I don't think I've applied it yet)- Clear the search field (
oauth->)- Select everything (
ctrl+a)Export selected itemsMore...->Reset preferencesIf that does not fix the problem, then you can reload your preferences from the file saved in step 4. If it does fix the problem, then it is a configuration setting somewhere.
Sorry for the delay
@taylor.smock i confirm the issue may be caused by some configuration setting. A preference reset got me back to step 2. Nominatim search does work on the 1st run, but then the issue returns when restarting JOSM. Resetted both oauth.access-token.key and oauth.access-token.secret in Advanced Preferences with the faulty configuration profile (2nd run onwards) and nothing has changed.
I tried to reproduce the issue on another physical machine, on both Windows 11 and Windows 7, and the same thing happens. I hadn't installed JOSM on Windows 7 yet. Logs here.
comment:7 by , 3 years ago
You are getting connection timeout errors. Best guess: flaky internet.
Try increasing the timeout from 15s to 30s or more.
comment:8 by , 3 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → needinfo |
comment:9 by , 3 years ago
| Resolution: | → needinfo |
|---|---|
| Status: | needinfo → closed |
I'm assuming that the timeout increase I mentioned in comment:7 fixed the issue. If that is wrong, feel free to correct me.
I've been unable to reproduce on Mac with Java 17. Unfortunately I do not have a Windows machine to test with.
Stupid question: Are you rate limited on Nominatim? (Next time this happens, does https://nominatim.openstreetmap.org/search?format=xml&q=roma work properly?)
If you are rate limited, please see where you may be violating the OSM Nominatim usage policy.
Also a possibility: something is changing the
socket.timeout.connectpreference from 15 seconds to something much less. From wiki:Help/Preferences/Advanced , JOSM Preferences -> enableExpert Mode->Advanced Preferences-> Search for and selectsocket.timeout.connect->Resetthe preference (there is a button at the bottom of the list for this).