commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Re: [commons-net] FTPClient setReceiveBufferSize() setSendBufferSize()
Date Thu, 23 Apr 2009 16:02:24 GMT
Ah, yes, that's the issue, thanks! Looking at it closer, though, does something similar also
need to be done when the data channel is opened in the FTPClient - for the active local mode?
That is, in _openDataConnection_, server.setReceiveBufferSize(receiveBufferSize) would also
need to be set? 



----- Original Message ----- 
From: "Rory Winston" <> 
To: "Commons Users List" <> 
Sent: Wednesday, April 22, 2009 5:34:40 PM GMT -07:00 US/Canada Mountain 
Subject: Re: [commons-net] FTPClient setReceiveBufferSize() setSendBufferSize() 

Hi Phil 

Actually, there was a long-standing latent bug in [net] where calls to 
set the socket buffer size were effectively ignored, as they were 
applied after the socket had been bound. This has recently been fixed 
in the 2.0 branch head. See:

So, as Steve says, you can either make these changes locally, or just 
download the latest source from the 2.0 branch and use that. 


On 22 Apr 2009, at 20:01, wrote: 

> I have an ftp connection that would greatly benefit from having very 
> large TCP/IP window sizes (1MB). I'm having trouble figuring out how 
> to implement this using the standard FTPClient. What's the intended 
> usage of setReceiveBufferSize() and setSendBufferSize(), which are 
> inherited from the SocketClient? 
> From what I understand, setReceiveBufferSize() must be set prior to 
> binding to the socket? However, if these methods are called prior to 
> FTPClient.connect(), then this socket object isn't initialized. 
> After FTPClient.connect(), is it too late? 
> Any insight into configuring the FTPClient to configure these window 
> sizes is greatly appreciated. 
> Thanks, 
> Phil 

To unsubscribe, e-mail: 
For additional commands, e-mail: 

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message