[
https://issues.apache.org/jira/browse/FTPSERVER-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712356#action_12712356
]
Niklas Gustavsson commented on FTPSERVER-304:
---------------------------------------------
I don't think this is how it is currently working (also, see FTPSERVER-258
where this have been discussed before). The way its supposed to work is:
* If the listener has a non-zero value, it provides the upper limit to the idle
time
* If the listener has a zero value, it is unlimited and thus the users limit is
used instead
* If the users limit is smaller than the listeners, it is used.
The code for this is in
org.apache.ftpserver.impl.FtpIoSession.setMaxIdleTime(int). If the code is not
working as expected, I'm happy to fix it (it sounds like it's not from Johannes
description).
Also, we need better documentation for this behavior. We should not close this
issue until the wiki has been updated.
> The Idle Timeout set in the listener configuration does not have any effect
> ---------------------------------------------------------------------------
>
> Key: FTPSERVER-304
> URL: https://issues.apache.org/jira/browse/FTPSERVER-304
> Project: FtpServer
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.1
> Reporter: Sai Pullabhotla
> Fix For: 1.0.2
>
>
> As reported on the mailing list by Johannes, I confirmed that the idle
> timeout set on the listener factory did not have any effect. The
> connection/session is still good long after the specified idle timeout. As
> far as I can remember this used to work fine in pre-1.0 releases. We also
> have to make sure that the idle timeout on the data connections works.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
