commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <>
Subject [jira] Commented: (NET-258) Implement A Keepalive Mechanism
Date Thu, 03 Mar 2011 12:33:37 GMT


Sebb commented on NET-258:


Just for the record, I did initial testing against Apache MINA ftpserver 1.0.5 and FileZilla
server 0.9.37 beta installed locally.

FileZilla allows concurrent control and data, but ftpserver does not (but then most public
ftp servers don't seem to either).

So luckily I was able to test both types quite easily during development.

I have also tried against several ASF ftp mirrors, and they seem to work.

What I have not been able to test is whether the NOOPs keep routers happy, because my router
does not seem to cause any problems - I'm not sure it has a connection timeout feature.

If you do have access to such a router, the FTPClientExample class can be used to test if
the keepalive helps.

> 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