Changes between Initial Version and Version 1 of Ticket #7875, comment 4


Ignore:
Timestamp:
2012-07-19T18:20:27+02:00 (13 years ago)
Author:
stoecker

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #7875, comment 4

    initial v1  
    11It would be important to find the root cause of the issue:
    22
    3 1) Java - does Java6 work?
    4 2) The OSM-server. When you call josm from commandline, you should see the requests send to the server. When you send such a request in the web-browser do you get full data (must start end end with same tag)?
    5 3) Maybe it is a simple delay and you need only to wait much longer?
    6 4) Currently the API is under a lot of stress due to the data redaction. Maybe that results in longer wait times. Try setting the variables socket.timeout.connect or socket.timeout.read to higher/lower values (you find them in expter mode under the last settings picture.
     3* Java - does Java6 work?
     4* The OSM-server. When you call josm from commandline, you should see the requests send to the server. When you send such a request in the web-browser do you get full data (must start end end with same tag)?
     5* Maybe it is a simple delay and you need only to wait much longer?
     6* Currently the API is under a lot of stress due to the data redaction. Maybe that results in longer wait times. Try setting the variables socket.timeout.connect or socket.timeout.read to higher/lower values (you find them in expter mode under the last settings picture.
    77
    88In any case, please report results.