[Cyberduck-trac] [Cyberduck] #11001: Maximum number of simultaneous transfers not handled properly
Cyberduck
trac at cyberduck.io
Thu May 13 12:08:57 UTC 2021
#11001: Maximum number of simultaneous transfers not handled properly
------------------------------------------+-------------------------
Reporter: jdevrie | Owner: dkocher
Type: defect | Status: reopened
Priority: high | Milestone: 7.9.0
Component: core | Version: 7.2.5
Severity: major | Resolution:
Keywords: error simultaneous transfers | Architecture: Intel
Platform: Windows 10 |
------------------------------------------+-------------------------
Changes (by KiddBarba):
* status: closed => reopened
* resolution: fixed =>
Old description:
> The number of simultaneous transfers is not handled properly. It can end
> up in not downloading anything anymore while there are still transfers
> queued. When changing the number in the box at the bottom of the
> transfers window up and down at some time nothing changes anymore in the
> real amount of transfers . When some time later all active transfers have
> ended the transfers still queued are all in the ""maximum allowed
> connections exceeded. Waiting..." state and none of those transfers are
> becoming active. So nothing is transfered anymore.
>
> What I have also seen is that the maximum # transfers is set to a certain
> nunber and there are already more transfers active thenthe nunber is the
> selct box but when I increase the maximum more transfers become active
> despite the fact that the number of active transfers was higher than the
> maximum in the box.
New description:
The number of simultaneous transfers is not handled properly. It can end
up in not downloading anything anymore while there are still transfers
queued. When changing the number in the box at the bottom of the transfers
window up and down at some time nothing changes anymore in the real amount
of transfers . When some time later all active transfers have ended the
transfers still queued are all in the ""maximum allowed connections
exceeded. Waiting..." state and none of those transfers are becoming
active. So nothing is transfered anymore.
What I have also seen is that the maximum # transfers is set to a certain
nunber and there are already more transfers active thenthe nunber is the
selct box but when I increase the maximum more transfers become active
despite the fact that the number of active transfers was higher than the
maximum in the box.
[UPDATE v.7.9.0]: When queued transfers in the download box are stopped
then resumed, CyberDuck stops limiting the maximum number of transfers
allowed. It downloads all transfers simultaneously instead of queuing
them.
--
--
Ticket URL: <https://trac.cyberduck.io/ticket/11001#comment:5>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows
More information about the Cyberduck-trac
mailing list