[
https://issues.apache.org/jira/browse/FTPSERVER-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sai Pullabhotla updated FTPSERVER-362:
--------------------------------------
Attachment: FTPSERVER-362.patch
For the most part I made the patch work like we have talked on the mailing
list. However, a few things note:
If max-threads is explicitly set and is a positive integer, a thread pool of
specified size will be created and shared across all listeners.
If max-threads is not explicitly set, but max-logins are set (explicit or
implicit), then max-threads = max-logins
If max-threads is not explicitly set, and if the max-logins is set to zero (0)
then max-threads become 16. This is due to the fact the we consider
max-logins=0 as unlimited. I had to choose some default for max-threads and
picked 16.
Let me know if this looks good and can be checked in.
Thanks.
> Add a configuration option for maximum number of threads the server is
> allowed to create
> ----------------------------------------------------------------------------------------
>
> Key: FTPSERVER-362
> URL: https://issues.apache.org/jira/browse/FTPSERVER-362
> Project: FtpServer
> Issue Type: New Feature
> Components: Core
> Affects Versions: 1.0.0-M1, 1.0.0-M2, 1.0.0-M3, 1.0.0-M4, 1.0.0-RC1,
> 1.0.0-RC2, 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4
> Reporter: Sai Pullabhotla
> Fix For: 1.0.5
>
> Attachments: FTPSERVER-362.patch
>
>
> Currently the max threads are defaulted to 16. Based on the discussion on the
> DEV mailing list, it would be nice to make this configurable.
> The thread on the mailing list is at -
> http://old.nabble.com/FTPServer-handling-of-multiple-concurrent-connections.-td28079420.html.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
