Maximum simultaneous transfers limit and server‑side connection pool exhaustion

Goal: understand how FileZilla Client reacts when the per‑server maximum simultaneous transfers limit is reached while the remote host begins to close idle connections, potentially exhausting its connection pool.

Constraints: the limit applies per server, pending transfers stay in the queue, and transfer mode (Passive/Active) influences firewall handling; it is unclear whether the client attempts to reuse a reset socket or waits for a free slot, and what back‑off logic, if any, is applied.

• Does FileZilla automatically retry a transfer after a server‑side connection reset, or does it keep the file queued until manual intervention?
• How does the client distinguish a temporary throttling event from a permanent connection‑limit condition when deciding to open a new socket?
• Is there an internal timeout or back‑off strategy that governs how long FileZilla waits for a slot to become available before aborting the transfer?