Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resuming file transfer starts over and errors out #9598

Closed
cyberduck opened this issue Jun 17, 2016 · 10 comments
Closed

Resuming file transfer starts over and errors out #9598

cyberduck opened this issue Jun 17, 2016 · 10 comments
Assignees
Labels
b2 bug fixed version:5.0
Milestone

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Jun 17, 2016

5bd5b0a created the issue

I have seen this behavior on Windows 10 and Windows 7, both 64 bit systems. I have seen the behavior with 5.0.1 and now 5.0.3 Cyberduck. I am seeing that the resume function does not work. It will simply start over in the upload process or error out. Is there something I am missing in getting the resume to work? Happy to send logs if you let me know which ones you need. Thanks, Jeff

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 15, 2016

@dkocher commented

Please attach the file cyberduck.log in the application support directory.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 20, 2016

8090bf5 commented

Can confirm the bug on v5.0.9 (20675) Win10 x64, backblaze b2

Cyberduck.log contains a single exception report:

2016-07-20 03:46:56,843 (http-vs2013.2.iso-1) ERROR ch.cyberduck.core.threading.LoggingUncaughtExceptionHandler - Thread http-vs2013.2.iso-1 has thrown uncaught exception:Connection pool shut down
java.lang.IllegalStateException: Connection pool shut down
	at org.apache.http.util.Asserts.check(Asserts.java:34)
	at org.apache.http.pool.AbstractConnPool.lease(AbstractConnPool.java:185)
	at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.requestConnection(PoolingHttpClientConnectionManager.java:251)
	at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:175)
	at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
	at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)
	at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
	at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107)
	at synapticloop.b2.request.BaseB2Request.execute(BaseB2Request.java:337)
	at synapticloop.b2.request.BaseB2Request.executePost(BaseB2Request.java:254)
	at synapticloop.b2.request.B2UploadPartRequest.getResponse(B2UploadPartRequest.java:57)
	at synapticloop.b2.B2ApiClient.uploadLargeFilePart(B2ApiClient.java:525)
	at ch.cyberduck.core.b2.B2PartWriteFeature$1.call(B2PartWriteFeature.java:81)
	at ch.cyberduck.core.b2.B2PartWriteFeature$1.call(B2PartWriteFeature.java:70)
	at ch.cyberduck.core.http.AbstractHttpWriteFeature$2.run(AbstractHttpWriteFeature.java:89)
	at ch.cyberduck.core.threading.NamedThreadFactory$1.run(NamedThreadFactory.java:55)
	at java.lang.Thread.run(Thread.java:953)

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 20, 2016

@dkocher commented

What is the error displayed when trying to resume the transfer?

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 20, 2016

8090bf5 commented

It tries to login, resume, fiddles for a while, then displays "Transfer incomplete". Screenshot is from Server 2012, but the behavior is about the same.

external image

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 27, 2016

@dkocher commented

#9622 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 29, 2016

@dkocher commented

In a5d1264.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 30, 2016

@dkocher commented

Fix resume in 065067c. Always use different upload URI for segments of large uploads for better reliability (94a42c7).

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 30, 2016

@dkocher commented

Please update to snapshot build 5.1.20726 or later which should fix this issues with large uploads to B2. Refer to https://trac.cyberduck.io/wiki/help/en/howto/preferences#Update on how to update to a snapshot build.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 4, 2016

5bd5b0a commented

I installed the snapshot build 5.1.20739 and I haven't seen any issues with the resume so far.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 4, 2016

@dkocher commented

Replying to [comment:12 jreiter1975]:

I installed the snapshot build 5.1.20739 and I haven't seen any issues with the resume so far.
Thanks for your confirmation!

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
b2 bug fixed version:5.0
Projects
None yet
Development

No branches or pull requests

2 participants