Modify

Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#7876 closed defect (duplicate)

NullPointerException when trying to resolve conflict on server during update

Reported by: torbjoern.k@… Owned by: team
Priority: normal Milestone:
Component: Core Version: tested
Keywords: Cc:

Description

During updating an existing dataset, JOSM told me that there is one datapoint, which might no longer exist on the server but locally on my computer.

When I hit "try to resolve on server" I'm getting the following error message (in German):

Daten herunterladen fehlgeschlagen. Das Format ist nicht unterstützt, unzulässig strukturiert und/oder inkonsistent.

Details (nicht übersetzt): java.lang.NullPointerException

As I've run JOSM from command line (with java -jar josm-tested.jar) this is the stacktrace I'm getting:

GET http://api.openstreetmap.org/api/0.6/nodes?nodes=262221757
org.openstreetmap.josm.io.OsmTransferException: org.openstreetmap.josm.io.IllegalDataException: java.lang.NullPointerException
        at org.openstreetmap.josm.io.MultiFetchServerObjectReader.multiGetIdPackage(MultiFetchServerObjectReader.java:306)
        at org.openstreetmap.josm.io.MultiFetchServerObjectReader.fetchPrimitives(MultiFetchServerObjectReader.java:413)
        at org.openstreetmap.josm.io.MultiFetchServerObjectReader.parseOsm(MultiFetchServerObjectReader.java:448)
        at org.openstreetmap.josm.gui.io.UpdatePrimitivesTask.realRun(UpdatePrimitivesTask.java:148)
        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:441)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:662)
Caused by: org.openstreetmap.josm.io.IllegalDataException: java.lang.NullPointerException
        at org.openstreetmap.josm.io.OsmReader.doParseDataSet(OsmReader.java:598)
        at org.openstreetmap.josm.io.OsmReader.parseDataSet(OsmReader.java:615)
        at org.openstreetmap.josm.io.MultiFetchServerObjectReader.multiGetIdPackage(MultiFetchServerObjectReader.java:302)
        ... 11 more
Caused by: java.lang.NullPointerException
        at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:989)
        at java.lang.Double.parseDouble(Double.java:510)
        at org.openstreetmap.josm.io.OsmReader.parseNode(OsmReader.java:180)
        at org.openstreetmap.josm.io.OsmReader.parseOsm(OsmReader.java:134)
        at org.openstreetmap.josm.io.OsmReader.parseRoot(OsmReader.java:104)
        at org.openstreetmap.josm.io.OsmReader.parse(OsmReader.java:90)
        at org.openstreetmap.josm.io.OsmReader.doParseDataSet(OsmReader.java:567)
        ... 13 more

Attachments (0)

Change History (4)

in reply to:  description comment:1 by Don-vip, 13 years ago

Replying to torbjoern.k@…:

As I've run JOSM from command line (with java -jar josm-tested.jar)

If you're running tested version, this may be due to #7847. Can you please try with latest ?

comment:2 by anonymous, 13 years ago

Yes, I've encountered this with the tested version. (sry, I forgot to select it in the bug report)

With the latest version it does work. No error any more. Thanks a lot.

comment:3 by anonymous, 13 years ago

Resolution: fixed
Status: newclosed
Version: tested

comment:4 by Don-vip, 13 years ago

Resolution: fixedduplicate

Closed as duplicate of #7847.

Last edited 13 years ago by Don-vip (previous) (diff)

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.