Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.0.6
-
None
-
None
Description
In several hours after start the server cannot accept passive connections if allowed passive ports are configured.
This is caused by FTPSERVER-420, org.apache.ftpserver.impl.PassivePorts.reserveNextPort() lines 218-219,
where the value removed from the freeList might be different from the value added to the usedList, if checkPortUnbound returns false before.
Attachments
Attachments
Issue Links
- relates to
-
FTPSERVER-481 Artificially running out of passive ports under load
- Open