[
https://issues.apache.org/jira/browse/FTPSERVER-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661277#action_12661277
]
Niklas Gustavsson commented on FTPSERVER-258:
---------------------------------------------
I would like the listener value (if set) to override any larger user value.
That would then enforce the maximum idle time, and the user store would enable
setting any specific user to a lower value. Or, you can use the user store
alone, in which case each users value would be used. What do you think?
Anyways, the patch is a good start, I'll use that and implement the solution
describe above for RC1 unless anyone complains.
> 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.
