commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bogdan Drozdowski (JIRA)" <>
Subject [jira] Commented: (NET-258) Implement A Keepalive Mechanism
Date Fri, 04 Mar 2011 12:54:36 GMT


Bogdan Drozdowski commented on NET-258:

Yes, you were lucky to find both types of servers that easily. I'm glad everything works.

Unfortunately, I don't have a router that looks into the traffic and handles FTP connections.
I don't think that such a router would disconnect the connection after a timeout (it should
be the server's job to do this), but I know that routes that interfere with FTP exist.

The only thing that is left to do is wait for user complaints (if there will be any). :)

> Implement A Keepalive Mechanism
> -------------------------------
>                 Key: NET-258
>                 URL:
>             Project: Commons Net
>          Issue Type: Improvement
>          Components: FTP
>    Affects Versions: 2.0
>            Reporter: Rory Winston
>             Fix For: 3.0
>         Attachments: ftp-keepalive.diff
> For routers/firewalls that terminate idle connections, a separate heartbeat mechanism
may need to be implemented to keep the control connection active.
> Some potential issues:
> * Synchronization between a heartbeat write and a __getReply() on an active control connection
> * Should use the NOOP command as a heartbeat signal;
> * Make the timeout configurable;
> * Default SocketImpl::setKeepAlive() wont do here.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message