Modify ↓
Opened 5 years ago
Last modified 2 months ago
#20788 new defect
RespondsCode from overpass completely wrong formatted
| Reported by: | skyper | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core | Version: | latest |
| Keywords: | template_report ResponseCode error overpass | Cc: |
Description
What steps will reproduce the problem?
- Download parents real quick several times in a row with download objects from overpass enabled.
- Get ResponsCode as something failed
What is the expected result?
A nice formatted message.
What happens instead?
Messed up message with lots of formatting syntax displayed
Please provide any additional information below. Attach a screenshot if possible.
I got this with 429 and 504, so it seems to be a general issue.
Relative:URL: ^/trunk Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Last:Changed Date: 2021-04-21 17:31:06 +0200 (Wed, 21 Apr 2021) Revision:17812 Build-Date:2021-04-22 01:30:59 URL:https://josm.openstreetmap.de/svn/trunk Last errors/warnings: - 16522.691 E: java.lang.NullPointerException - 16522.692 E: java.lang.NullPointerException - 16637.969 E: java.lang.NullPointerException - 17879.824 W: javax.net.ssl.SSLException: Socket closed. Cause: javax.net.ssl.SSLException: Socket closed. Cause: java.net.SocketException: Socket closed - 17879.824 E: javax.net.ssl.SSLException: Socket closed. Cause: javax.net.ssl.SSLException: Socket closed. Cause: java.net.SocketException: Socket closed - 17895.953 E: org.openstreetmap.josm.io.OsmApiException: ResponseCode=429, Error Header=<rate_limited. Please check /api/status for the quota of your IP address.>, Error Body=<<?xml version="1.0" encoding="UTF-8"?> - 17895.953 E: org.openstreetmap.josm.io.OsmApiException: ResponseCode=429, Error Header=<rate_limited. Please check /api/status for the quota of your IP address.>, Error Body=<<?xml version="1.0" encoding="UTF-8"?> - 18430.842 E: javax.net.ssl.SSLException: Socket closed. Cause: java.net.SocketException: Socket closed - 19238.788 E: org.openstreetmap.josm.io.OsmApiException: ResponseCode=504, Error Header=<timeout. The server is probably too busy to handle your request.>, Error Body=<<?xml version="1.0" encoding="UTF-8"?> - 19238.789 E: org.openstreetmap.josm.io.OsmApiException: ResponseCode=504, Error Header=<timeout. The server is probably too busy to handle your request.>, Error Body=<<?xml version="1.0" encoding="UTF-8"?>
Attachments (1)
Change History (5)
comment:1 by , 5 years ago
| Version: | → latest |
|---|
comment:2 by , 5 years ago
| Summary: | RespondsCode from overpass complete wrong formatted → RespondsCode from overpass completely wrong formatted |
|---|
comment:3 by , 2 months ago
comment:4 by , 2 months ago
Far too much text for a single line in a popup. The console log is easier to read, but maybe we should just try to extract the message "timeout. The server is probably too busy ... "?
Note:
See TracTickets
for help on using tickets.



Got a similar message from the overpass API, popup is not well formatted. The console log shows
2025-11-02 07:40:35.930 SEVERE: org.openstreetmap.josm.io.OsmApiException: ResponseCode=504, Error Body=< OSM3S Response The data included in this document is from www.openstreetmap.org. The data is made available under ODbL. Error: runtime error: open64: 0 Success /osm3s_osm_base Dispatcher_Client::request_read_and_idx::timeout. The server is probably too busy to handle your request. > org.openstreetmap.josm.io.OsmApiException: ResponseCode=504, Error Body=< OSM3S Response The data included in this document is from www.openstreetmap.org. The data is made available under ODbL. Error: runtime error: open64: 0 Success /osm3s_osm_base Dispatcher_Client::request_read_and_idx::timeout. The server is probably too busy to handle your request. > at org.openstreetmap.josm.io.OsmServerReader.getInputStreamRaw(OsmServerReader.java:220) at org.openstreetmap.josm.io.OverpassDownloadReader.getInputStreamRaw(OverpassDownloadReader.java:346) at org.openstreetmap.josm.io.OsmServerReader.getInputStreamRaw(OsmServerReader.java:126) at org.openstreetmap.josm.io.OsmServerReader.getInputStream(OsmServerReader.java:90) at org.openstreetmap.josm.io.OsmServerReader.getInputStream(OsmServerReader.java:73) at org.openstreetmap.josm.io.BoundingBoxDownloader.parseOsm(BoundingBoxDownloader.java:213) at org.openstreetmap.josm.io.OverpassDownloadReader.parseOsm(OverpassDownloadReader.java:403) at org.openstreetmap.josm.actions.downloadtasks.DownloadOsmTask$DownloadTask.parseDataSet(DownloadOsmTask.java:470) at org.openstreetmap.josm.actions.downloadtasks.DownloadOsmTask$DownloadTask.realRun(DownloadOsmTask.java:478) at org.openstreetmap.josm.gui.PleaseWaitRunnable.doRealRun(PleaseWaitRunnable.java:94) at org.openstreetmap.josm.gui.PleaseWaitRunnable.run(PleaseWaitRunnable.java:142) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.base/java.util.concurrent.FutureTask.run(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source) 2025-11-02 07:40:36.023 SEVERE: Communication with OSM server failed - ResponseCode=504, Error Body=< OSM3S Response The data included in this document is from www.openstreetmap.org. The data is made available under ODbL. Error: runtime error: open64: 0 Success /osm3s_osm_base Dispatcher_Client::request_read_and_idx::timeout. The server is probably too busy to handle your request. >