null pointer exception on all uploads

[vbroman@…]

since r1566 every (just about?) upload of edits I've done
results in a java null pointer exception signaled with
a popup window. I am unsure how much of the upload, if anything
succeeds in arriving. JOSM seems to add the old changes to
the next upload cumulatively. I tried "-latest" in a console
window, so I could see the following

PUT ​http://www.openstreetmap.org/api/0.6/changeset/create... OK
POST ​http://www.openstreetmap.org/api/0.6/changeset/1092597/upload... Unprocessable Entity
PUT ​http://www.openstreetmap.org/api/0.6/changeset/1092597/close... OK

I don't know how to compile the subversion latest version,
though if I got hints, I might be to try it.

[anonymous]

I did find a street, a way including node 49064045,
which had a tiger:tlid longer than 255 characters.
I tried shortening it, then deleting it.
I still fail in uploading all my changes, as below.
"Unprocessable" needs to be made more explicit, I guess -- what cannot be processed?

GET ​http://www.openstreetmap.org/api/capabilities... OK
Communications with ​http://www.openstreetmap.org/api established using protocol version 0.6
PUT ​http://www.openstreetmap.org/api/0.6/changeset/create... OK
POST ​http://www.openstreetmap.org/api/0.6/changeset/1134765/upload... Internal Server Error
POST ​http://www.openstreetmap.org/api/0.6/changeset/1134765/upload... Unprocessable Entity
Error body:

PUT ​http://www.openstreetmap.org/api/0.6/changeset/1134765/close... OK
GET ​http://www.openstreetmap.org/api/capabilities... OK
Communications with ​http://www.openstreetmap.org/api established using protocol version 0.6
PUT ​http://www.openstreetmap.org/api/0.6/changeset/create... OK
POST ​http://www.openstreetmap.org/api/0.6/changeset/1134801/upload... Unprocessable Entity
Error body:

PUT ​http://www.openstreetmap.org/api/0.6/changeset/1134801/close... OK

The error body returned seems to be empty, and the pop-up message window generated is blank.
Now I'm not getting the Null Pointer anymore, though.

[Gubaer]

It seems that way ​49064045 does not cause the error.

• it's length is exactly 255
• changeset ​1135575 shows that a node can be added to an area which includes way ​49064045
• changeset ​1135582 shows that way ​49064045 can be updated

Unprocessable Entity doen't seem to be an error code in the ​API 0.6, neither is it a standard status code for ​HTTP.

Can you post the smallest possible OSM file which causes the problem when uploading?

[anonymous]

I only have a very large osm file that I've done much with.
It appears that r1590 works for me now.
There was a useful error message from the upload,
and I could fix the relevant too-long tlid and a version conflict.
So now I'm unstuck. Thanks.