You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "SlackJack (JIRA)" <ji...@apache.org> on 2013/07/18 15:20:49 UTC

[jira] [Closed] (FTPSERVER-444) DefaultFtpServer.stop() removes default listener from FtpServerFactory

     [ https://issues.apache.org/jira/browse/FTPSERVER-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

SlackJack closed FTPSERVER-444.
-------------------------------

       Resolution: Not A Problem
    Fix Version/s: 1.0.6

JavaDoc of DefaultFtpServer.stop() states that a stopped server cannot be started with DefaultFtpServer.start() again. The bug is therefore not a bug, but a feature request at most.
                
> DefaultFtpServer.stop() removes default listener from FtpServerFactory
> ----------------------------------------------------------------------
>
>                 Key: FTPSERVER-444
>                 URL: https://issues.apache.org/jira/browse/FTPSERVER-444
>             Project: FtpServer
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 1.0.6
>         Environment: Java 1.7, Windows 64
>            Reporter: SlackJack
>             Fix For: 1.0.6
>
>
> When using the default classes in an embedded environment, the following situation arises:
> -Configure FtpServerFactory with addListener("default", someListener)
> -Create server via FtpServerFactory.createServer()
> -Start / stop the created FTPServer instance
> -Create a new server instance with FtpServerFactory.createServer()
> -new server does not have a listener. in fact, the FtpServerFactory listener map gets cleared the moment the first FtpServer.stop() is called.
> In my opinion, this problem occurs because the FtpServerFactory is assigned to the same DefaultFtpServerContext as the server instances, which clear the listener maps on FtpServer.stop(). This should not happen, since the FtpServerFactory and its Context must be out-of-scope for the FtpServer instances.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira