Modify ↓
#11071 closed defect (othersoftware)
error in upload datas to OSM server
Reported by: | Xapitoun | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | latest |
Keywords: | template_report api xml | Cc: |
Description
What steps will reproduce the problem?
- send datas to OSM server
What is the expected result?
all datas are uploaded to OSM server
What happens instead?
sometimes you have this kind of error. I tried to use JOSM 8008 with the same datas but I found the same problem.
Please provide any additional information below. Attach a screenshot if possible.
Repository Root: http://josm.openstreetmap.de/svn Build-Date: 2015-02-05 02:34:52 Last Changed Author: Klumbumbus Revision: 8008 Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Relative URL: ^/trunk URL: http://josm.openstreetmap.de/svn/trunk Last Changed Date: 2015-02-04 22:44:51 +0100 (Wed, 04 Feb 2015) Last Changed Rev: 8008 Identification: JOSM/1.5 (8008 en) Linux ubuntu 13.10 Memory Usage: 425 MB / 878 MB (101 MB allocated, but free) Java version: 1.7.0_55, Oracle Corporation, OpenJDK 64-Bit Server VM Java package: openjdk-7-jre:amd64-7u55-2.4.7-1ubuntu1~0.13.10.1 Dataset consistency test: No problems found Plugins: - OpeningHoursEditor (30892) - RoadSigns (30892) - ShapeTools (1000) - buildings_tools (30892) - download_along (30892) - geotools (30892) - imagery-xml-bounds (30892) - imagery_offset_db (30892) - imageryadjust (30892) - jts (30892) - mapdust (30892) - mirrored_download (30892) - notes (v0.9.5) - opendata (30911) - reltoolbox (30892) - reverter (30892) - todo (29154) - turnlanes (30892) - turnrestrictions (30892) - undelete (30892) - utilsplugin2 (30892) - wikipedia (30892) Last errors/warnings: - E: Broken tagging preset "surface-Surface" - number of items in 'display_values' must be the same as in 'values' - E: Broken tagging preset "surface-Surface" - number of items in 'display_values' must be the same as in 'values' - W: Cannot start remotecontrol server on port 8111: Address already in use - E: org.openstreetmap.josm.io.OsmTransferException: org.openstreetmap.josm.tools.XmlParsingException: Content is not allowed in prolog. - E: org.openstreetmap.josm.io.OsmTransferException: org.openstreetmap.josm.tools.XmlParsingException: Content is not allowed in prolog. org.openstreetmap.josm.io.OsmTransferException: org.openstreetmap.josm.tools.XmlParsingException: Content is not allowed in prolog. org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Content is not allowed in prolog. at org.openstreetmap.josm.io.OsmApi.uploadDiff(OsmApi.java:554) at org.openstreetmap.josm.io.OsmServerWriter.uploadChangesInChunks(OsmServerWriter.java:172) at org.openstreetmap.josm.io.OsmServerWriter.uploadOsm(OsmServerWriter.java:214) at org.openstreetmap.josm.gui.io.UploadPrimitivesTask.realRun(UploadPrimitivesTask.java:248) at org.openstreetmap.josm.gui.PleaseWaitRunnable.doRealRun(PleaseWaitRunnable.java:93) at org.openstreetmap.josm.gui.PleaseWaitRunnable.run(PleaseWaitRunnable.java:161) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: org.openstreetmap.josm.tools.XmlParsingException: Content is not allowed in prolog. org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Content is not allowed in prolog. at org.openstreetmap.josm.io.DiffResultProcessor.parse(DiffResultProcessor.java:90) at org.openstreetmap.josm.io.OsmApi.uploadDiff(OsmApi.java:546) ... 8 more Caused by: org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Content is not allowed in prolog. 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:441) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:368) at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1436) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:999) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:606) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:848) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:649) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:333) at org.openstreetmap.josm.io.DiffResultProcessor.parse(DiffResultProcessor.java:86) ... 9 more
Attachments (0)
Change History (3)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
Keywords: | api xml added |
---|---|
Resolution: | → othersoftware |
Status: | new → closed |
It happens when the OSM API returns garbage. Please file a ticket to OSM API developers by mentioning your changeset number.
Note:
See TracTickets
for help on using tickets.
Similar to #8097