[
https://issues.apache.org/jira/browse/FTPSERVER-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713055#action_12713055
]
Sai Pullabhotla commented on FTPSERVER-304:
-------------------------------------------
gets
You wrote:
Not sure what you meant by that.
currently, if the user's timeout is set to zero, the session never times
out. It does not use the listener's timeout.
I think most/all FTP servers that I've worked with have a global timeout
option that can be overriddden at a user level. Have not seen the
"max-idle-time" option. So, I guess, we should treat our listener timeout as
default-timeout instead of max-timeout. It would help if other users in the
group throw in their ideas too.
Sai Pullabhotla
www.jMethods.com
On Mon, May 25, 2009 at 2:18 PM, Niklas Gustavsson (JIRA)
<[email protected]>wrote:
> 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.
