[
https://issues.apache.org/jira/browse/FTPSERVER-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711449#action_12711449
]
Sai Pullabhotla commented on FTPSERVER-304:
-------------------------------------------
After researching into this issue...here is what I found.
The idle timeout set on the listener does in fact work until the user logs in.
Once the user logs in, the idle timeout is taken from the "User" object and set
on the session. In my case, I left the idle timeout for the user at zero
(perhaps, so did the original poster) which makes the timeout infinite.
At this point I'm not sure how exactly we wanted the behavior to be. But I
would recommend the following:
1. By default all users should inherit the timeout specified in the listener
configuration.
2. Timeout can be overridden at a specific user level by setting it to a value
>= 0, where 0 means do not timeout.
3. Any negative value specified for the user timeout should be interpreted as
use the default timeout (the timeout specified on the listener).
4. Update the BaseUser class to default the idle timeout to -1 (in the
constructor).
Basically by allowing the timeout inheritance, there is no need to have a
timeout specified on every user's record.
Let me know what you guys think.
> 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 conformed 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.
