[
https://issues.apache.org/jira/browse/FTPSERVER-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Kuhn updated FTPSERVER-258:
--------------------------------
Attachment: idletime.patch
It makes sense. I think that my idea can be merged with yours.
Idle time is zero or positive value. All these values have defined meaning - no
limit or a limit. You cannot say just to use a default value. If we permit
users to have undefined idle time value (something like null) there is a clear
way to use listener's one.
See attached patch (idletime.patch) for details.
Note:
Negative idle times for listeners are prohibited - see
org.apache.mina.core.session.AbstractIoSessionConfig#setIdleTime(IdleStatus,
int)
> 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, idletime.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.
