Modify

Opened 12 years ago

Closed 12 years ago

#8278 closed defect (fixed)

Failing to download from API

Reported by: sabas88@… Owned by: team
Priority: normal Milestone:
Component: Core Version:
Keywords: api, sax, download Cc:

Description

Since some days Josm cannot download the data from the API. The error window says the connection initialization failed.

I started josm from terminal and here's the error I have

org.openstreetmap.josm.io.OsmApiInitializationException: org.xml.sax.SAXParseException; lineNumber: 22; columnNumber: 3; The element type "meta" must be terminated by the matching end-tag "</meta>".
	at org.openstreetmap.josm.io.OsmApi.initialize(OsmApi.java:261)
	at org.openstreetmap.josm.io.OsmApi.initialize(OsmApi.java:202)
	at org.openstreetmap.josm.io.OsmServerReader.getInputStream(OsmServerReader.java:46)
	at org.openstreetmap.josm.io.BoundingBoxDownloader.parseOsm(BoundingBoxDownloader.java:135)
	at org.openstreetmap.josm.actions.downloadtasks.DownloadOsmTask$DownloadTask.parseDataSet(DownloadOsmTask.java:171)
	at org.openstreetmap.josm.actions.downloadtasks.DownloadOsmTask$DownloadTask.realRun(DownloadOsmTask.java:178)
	at org.openstreetmap.josm.gui.PleaseWaitRunnable.doRealRun(PleaseWaitRunnable.java:82)
	at org.openstreetmap.josm.gui.PleaseWaitRunnable.run(PleaseWaitRunnable.java:145)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
	at java.lang.Thread.run(Thread.java:679)
Caused by: org.xml.sax.SAXParseException; lineNumber: 22; columnNumber: 3; The element type "meta" must be terminated by the matching end-tag "</meta>".
	at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:198)
	at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177)
	at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:391)
	at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1404)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1726)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2915)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:625)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:488)
	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:819)
	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:748)
	at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:123)
	at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1208)
	at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:525)
	at javax.xml.parsers.SAXParser.parse(SAXParser.java:392)
	at org.openstreetmap.josm.io.OsmApi.initialize(OsmApi.java:220)
	... 13 more

Attachments (0)

Change History (7)

comment:1 by bastiK, 12 years ago

You should get a line

GET http://api.openstreetmap.org/api/...

on the command line before the stack trace.
What is the output if you download manually, e.g.

wget 'http://api.openstreetmap.org/api/capabilities'

?

comment:2 by anonymous, 12 years ago

No GET request appear on the terminal..

The wget request you wrote works.

comment:4 by sabas88@…, 12 years ago

That was easy!
Thanks a lot!

Stefano

comment:5 by Don-vip, 12 years ago

Resolution: fixed
Status: newclosed

comment:6 by bastiK, 12 years ago

Resolution: fixed
Status: closedreopened

We could handle this better. If the XML document cannot be successfully parsed, it should not end up in cache.

comment:7 by Don-vip, 12 years ago

Resolution: fixed
Status: reopenedclosed

In 5635/josm:

fix #8278 - Robustness in capabilities cache parsing at startup

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.