incubator-ftpserver-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niklas Gustavsson (JIRA)" <>
Subject [jira] Closed: (FTPSERVER-75) Extraneous connection cleanup timer.
Date Mon, 26 Feb 2007 22:13:06 GMT


Niklas Gustavsson closed FTPSERVER-75.

       Resolution: Fixed
    Fix Version/s:     (was: 1.0-M1)
         Assignee: Niklas Gustavsson

commit -m "No only creates default context in FtpServer if needed, not always.
Stale connection timer now created as a daemon timer. (both FTPSERVER-75)" C:/home/niklas/workspaces/apache/ftpserver/core/src/java/org/apache/ftpserver/
    Sending        C:/home/niklas/workspaces/apache/ftpserver/core/src/java/org/apache/ftpserver/
    Sending        C:/home/niklas/workspaces/apache/ftpserver/core/src/java/org/apache/ftpserver/listener/
    Transmitting file data ...
    Committed revision 512035.

Thanks for the report!

> Extraneous connection cleanup timer.
> ------------------------------------
>                 Key: FTPSERVER-75
>                 URL:
>             Project: FtpServer
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0-M1
>         Environment: Svn trunk as of r511633.
>            Reporter: Mark Reynolds
>         Assigned To: Niklas Gustavsson
>            Priority: Minor
>             Fix For: 1.0-M2
> FtpServer creates an instance of DefaultFtpServerContext which configures a ConnectionManagerImpl
in its constructor, which in turn starts a Timer. If the DefaultFtpServerContext is replaced
via the FtpServer's one-argument constructor, the timer in the dereferenced DefaultFtpServerContext
is never cancelled and keeps on running once a minute.
> Also, shouldn't this be a daemon timer?

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message