[
https://issues.apache.org/jira/browse/FTPSERVER-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661140#action_12661140
]
Jiri Kuhn commented on FTPSERVER-258:
-------------------------------------
There are two sources of idle time values - one is NioListener, other BaseUser.
If we imagine that user's maxidletime takes effect, user's value always wins. I
propose to have special idle time value for users (let's say -1) which would
say to PASS command not to update the session's value (coming from listener).
Without it, the listener's idle time would be quite useless. The only ability
will be to time out sessions without logged user.
> User's maxIdleTime doesn't work
> -------------------------------
>
> Key: FTPSERVER-258
> URL: https://issues.apache.org/jira/browse/FTPSERVER-258
> Project: FtpServer
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.0-M4
> Reporter: Jiri Kuhn
> Attachments: FtpIoSession.patch
>
>
> Setting user's maxidletime property has no effect, only working idle time is
> the one provided by NioListener which is global.
> The user's maxidletime is stored into ftp session as an attribute during PASS
> command, but nothing else happens. Idle event is completely handled by Mina
> and Mina has no knowledge about ftpserver's value. Mina takes the idle time
> from IoSessionConfig which is instantiated during NioListener construction
> (more precisely - during NioListener's SocketAcceptor construction). Each
> created session has its own copy of the config. That's my understanding and I
> hope it's right.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
