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

Connection lost regularly #8634

Closed
cyberduck opened this issue Mar 4, 2015 · 14 comments
Closed

Connection lost regularly #8634

cyberduck opened this issue Mar 4, 2015 · 14 comments
Assignees
Labels
bug fixed openstack OpenStack Swift Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

cyberduck commented Mar 4, 2015

9a602bf created the issue

Since I updated to 4.6.5 (17000), I have huge problems with the connection via Swift Openstack. The connection is lost after nearly every step (change folder, up/download files, etc.). The initial connection need several tries until it's opened. Rolled back to 4.6.4 16110 - no problems there. Connecting via HTTP proxy (but also happening without proxy, direct network access to the storage).

I guess it has something to do with the new multiple transfers.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Mar 4, 2015

@dkocher commented

Please try 446015a or later.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Mar 4, 2015

@dkocher commented

#8635 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Mar 5, 2015

@dkocher commented

#8637 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Mar 5, 2015

@dkocher commented

Reopen for #8635#comment:2.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Mar 21, 2015

@dkocher commented

Other potential fix in 8b66eab. From the Http Components release notes

Non-blocking connection should not trigger end-of-stream callback as long as there is still data in the session input buffer. This can cause a series of short pipelined requests to fail prematurely in case of an unexpected connection termination by the opposite endpoint.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Mar 31, 2015

@dkocher commented

#8651 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Mar 31, 2015

@dkocher commented

Please try f3bd48c or later.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Apr 1, 2015

@dkocher commented

This issue was caused by a bug in the HTTP library.

[HTTPCLIENT-1609] Stale connection check in PoolingHttpClientConnectionManager has no effect. Internal connection pool does not correctly implement connection validation.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Apr 1, 2015

@dkocher commented

Reverted in 0d8b40a.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Apr 1, 2015

@dkocher commented

Updated library dependency with fix in 157d5ce.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Apr 20, 2015

@dkocher commented

Please update to the latest snapshot build available.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Apr 20, 2015

9a602bf commented

The file list still won't update after uploading a file, only restarting build 17342 helps with that. Also after deleting or moving a file.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Apr 20, 2015

@dkocher commented

Replying to [comment:13 stefan jacobi]:

The file list still won't update after uploading a file, only restarting build 17342 helps with that. Also after deleting or moving a file.

This separate issue #8651 just got fixed in 4279b3e.

@cyberduck
Copy link
Collaborator Author

cyberduck commented May 13, 2015

@dkocher commented

#8697 closed as duplicate.

@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
bug fixed openstack OpenStack Swift Protocol Implementation
Projects
None yet
Development

No branches or pull requests

2 participants