Opened 12 years ago

Last modified 6 years ago

#3401 closed Bug report

Limiting connections to a certain server doesn't work

Reported by: karatedog Owned by:
Priority: normal Component: Other
Keywords: Cc: karatedog, Tim Kosse, Alexander Schuch
Component version: Operating system type:
Operating system version:

Description

I'd like to download 2 files at the same time from different servers, but to every server I have only 1 available connection, so I want to limit the number of connection to each of the servers to 1 (so when a filelist from one server runs out, the Client won't continue to download 2 files - now from the same server).

I set "Maximum simultaneous transfers" to 2, as I want to download 2 files at the same time.
Under Site manager I set server #1's "Transfer settings/Limit number of simultaneous connections" to 1, and I do the same to Server #2.
In the queue, I have 30+ files from Server #1, and have only 1 file from server #2, in this order.
Starting the queue will start to download 2 files from Server #1 :-(
I have to set that single file's priority to high or highest to make the Client do it right. But after that single file got downloaded, the Client tries to start a second connection on Server #1.
My opinion is that the Transfer settings are not taken into account, or they wont override the Max. transfer property.

I tried the following situation:

  • 1 server
  • 30+ files
  • Maximum simultaneous connection set to 5
  • the Server's "Limit number of simultaneous connections" set to 1

In this scenario - if the latter property overrode the former - only 1 file should be downloading at the same time. But this starts 5 download attempt.

Change History (6)

comment:1 Changed 12 years ago by karatedog

Windows XP, latest version of FileZilla Client (3.0.6)

comment:2 Changed 12 years ago by Tim Kosse

I can not reproduce this problem.

Please give detailed step by step instructions how to reproduce it.

comment:3 Changed 12 years ago by karatedog

I couldn't reproduce the same problem above, but I could create another one, and tested it several times. I have a server with unlimited possible connections, and before executing the steps below, the Client's max. transfer is set to 1, the server's "maximum number of connection" is disabled, and the queue is empty.

  1. step: Start the Client
  2. step: set the max transf. to 5
  3. step: set the server's "maximum number of connections" to 3
  4. step: open the server, and navigate to a directory
  5. step: right-click and select Download

Only 2 files are downloading at the same time, and this is reproducable.

In the meantime I found the solution. The Client needs to be restarted to make it work. I think this is the reason I couldn't reproduce the problem above, as I haven't restarted the Client between changing settings (maybe some settings are "stuck")

comment:4 Changed 12 years ago by Tim Kosse

FileZilla considers servers which only differ in the "maximum number of connections" setting to be completely different. As such, changes made in the site manager do not affect already queued files or active connections.

comment:5 Changed 12 years ago by karatedog

Look at the steps I wrote. There is no connection to the server, and the queue is empty, when I change those settings. THEN I open the connection, fill the queue, and start the queue.
And there is no second server to make a difference, I used only one server.

comment:6 Changed 12 years ago by Tim Kosse

  1. step: set the server's "maximum number of connections" to 3
  2. step: open the server, and navigate to a directory
  3. step: right-click and select Download

Only 2 files are downloading at the same time, and this is reproducable.

1 browsing and 2 transfer connections = 3 total.

Note: See TracTickets for help on using tickets.