Cyberduck
Mountain Duck
CLI#9443 closed defect (worksforme)
Connection reset during upload
| Reported by: | jimgoldstein | Owned by: | |
|---|---|---|---|
| Priority: | highest | Milestone: | 4.9.1 |
| Component: | b2 | Version: | Nightly Build |
| Severity: | blocker | Keywords: | |
| Cc: | Architecture: | ||
| Platform: |
Description
Started up my download with the latest version of Cyberduck. I updated the app this morning to v. 5.0 (19720) I'm trying to complete the attached upload and a Java.net.SocketException error is coming up. When this happens the transfer stops and I have to start again. This is a loop and no transfers are happening so far today.
Attachments (1)
Change History (5)
Changed on Apr 12, 2016 at 6:35:40 PM by jimgoldstein
comment:1 Changed on Apr 12, 2016 at 8:19:03 PM by dkocher
- Component changed from core to b2
- Summary changed from Java.net.SocketException Error to Connection reset during upload
comment:2 Changed on Apr 13, 2016 at 11:50:05 AM by dkocher
comment:3 Changed on Apr 13, 2016 at 11:52:44 AM by dkocher
https://www.backblaze.com/b2/docs/integration_checklist.html
During an upload using the b2_upload_file or b2_upload_part API, if one of the following conditions occur, the developer should call b2_get_upload_url or b2_get_upload_part_url and re-attempt the upload using the new URL and auth key pair:
- If an HTTPS connection cannot be made. (e.g., connection timeout)
- The HTTPS connection is broken. (e.g., broken pipe.)
comment:4 Changed on Apr 15, 2016 at 2:16:12 PM by dkocher
- Milestone set to 4.9.1
- Resolution set to worksforme
- Status changed from new to closed
Reviewed error handling in r20178.
Note: See
TracTickets for help on using
tickets.
The failure should be mapped as a connection refused failure type and then the upload should be re-attempted. Instead it is mapped to a interoperability failure which is not retried.