Modify ↓
Opened 17 years ago
Closed 17 years ago
#187 closed defect (wontfix)
Behaviour with connection problems
| Reported by: | maarten | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | Core | Version: | latest |
| Keywords: | Cc: |
Description
When JOSM seems unable to connect to the OSM server (the downloading or uploading box shows no activity), pressing cancel seems to do nothing. You can close the box with the [x] button. When you do this, all subsequent attempts to down- or upload data do not even show a download or upload box.
Attachments (0)
Note:
See TracTickets
for help on using tickets.
Looks like Java cannot close a connection with a TCP-RST asynchron. This means, I always have to wait until the server at least response with *something*.
I know... giving, that the current servers implementation take almost all the time at connection, the cancel button does not make much sense but is better than nothing.
The closing via [x] button works, but you will have to wait until the last connection has been timed out. I hope this will change sometimes when better server API implementations are available.
If you know a way to asynchronous kill a TCP-Connection in Java, reopen this and tell me. ;-)