[
https://issues.apache.org/jira/browse/FTPSERVER-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712570#action_12712570
]
Sai Pullabhotla commented on FTPSERVER-304:
-------------------------------------------
It appears to have been implemented just like how you described. In my case,
I've my listener timeout set to 300 seconds (upper limit) and all users'
timeout is set to 0. The third point you mentioned -
* If the users limit is smaller than the listeners, it is used.
0 is numerically smaller than 300, but when talking about Java timeouts, 0
(infinite) is greater than 300. Is this correct?
Also, It would be nice in some cases for all users to just inherit the listener
timeout. So, today my network policy is all connections would timeout after 300
seconds of idle time. After a month, my network policy changes and want all
connections to timeout in 120 seconds. In this case, If I've 500 users, I've to
update all 500 user records, which is a lot of work. How can we support this?
> 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.
