commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Watson, John" <>
Subject net:FtpClient connection problem
Date Mon, 12 Jul 2004 10:56:19 GMT
I'm new to this list and wondered if anyone can help.  I've been using the
commons net package 1.1.0.  I have an ftp client program that uses this
package and is continuously active.  It has 5 or 6 different threads each of
which queries different directories on an FTP server.  Each thread has a
separate FtpClient instance.  A thread wakes up after 5 minutes, gets a new
FtpClient connection and attempts to copy any new files it finds posted in
its directory.  It then disconnects (within a finally statement)
irrespective of whether it got errors.

What I find is that after some time of running (sometimes 2-3 days,
sometimes 2-3 weeks) I can no longer get a connection.  I see: No buffer space available (maximum connections
reached?): JVM_Bind
	at Method)
	at com.sis.ftpdupit.FtpWorker.syncFiles(Unknown Source)
	at Source)

I cannot see from my code how it would ever fail to call
FtpClient.disconnect().   Can anyone help?   (Incidentally, from today I am
investigating the current 1.2.2 release in the hope that such a problem
might have been corrected there).  Thanks in advance,

John Watson

Satellite Information Services Limited Registered Office: 
17 Corsham Street London N1 6DR, Company No. 4243307

The information in this e-mail (which includes any files 
transmitted with it) is confidential and may also be legally 
privileged.  It is intended for the addressee only.  Access to 
this e-mail by anyone else is unauthorised.  It is not to be 
relied upon by any person other than the addressee except 
with prior written approval of an authorised representative of 
SIS.  If no such approval is given, SIS will not accept any 
liability (in negligence or otherwise) arising from any third 
party acting, or refraining from acting, on such information.  

Unauthorised recipients are required to maintain confidentiality.
If you have received this e-mail in error please notify the 
sender immediately, destroy any copies and delete it from your
computer system.  

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