commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <gerard.vanw...@prorail.nl>
Subject [net] FTPClient.setSoTimeout() works difference in commons net 2.0 than early version?
Date Fri, 05 Nov 2010 15:00:42 GMT
Hello,

 

Can someone explain the difference between FTPClient.setSoTimeout() from
Commons Net 1.3 and 2.0.

 

I want to use the soTimeout in combination with FTPClient.storeFile();

 

Example:

FTPClient.setSoTimeout(10000); // 10 sec.

 

Upload speed is limited to 5 Kb per second (on the ftpserver).

The size of the file to upload is 100 Kb, so I thought that after the
timeout expires, a SocketTimeOutException is thrown, even if there is
still data communication between the FTPClient and the FTP server.

 

That SocketTimeOutException is thrown with Commons Net 1.3 but isn't
thrown with Commons Net 2.0. Can someone explain this to me?

 

Regards,

 

Gerard 

Deze e-mail en de inhoud daarvan is vertrouwelijk.
Het is mogelijk dat tijdens het opstellen of het transport van dit bericht fouten zijn ontstaan
zodat het bericht onjuist of onvolledig is overgekomen of verkeerd is geadresseerd. Hiervoor
kan ProRail geen aansprakelijkheid erkennen. Uitsluitend een document dat door een bevoegd
persoon namens ProRail is ondertekend is bindend. De inhoud van dit bericht mag niet openbaar
worden gemaakt, vermenigvuldigd of worden verspreid aan derden. Wij verzoeken u om bij twijfel
over de juistheid, de volledigheid of de adressering de e-mail direct te retourneren en daarna
te vernietigen. 

 
This e-mail and its contents are confidential.
It is possible that during the making or transmission of this message errors have arisen,
so that this message is improperly or incompletely dispatched or has wrongfully been addressed.
In this case, ProRail cannot be held liable. Only a document which has been signed by an authorized
person on behalf of ProRail is binding. The contents of this e-mail may not be disclosed,
copied or dispatched to anyone. In case of doubt about the correctness, the completeness or
the address, you are requested to reply the e-mail immediately and then destroy the e-mail.

Mime
  • Unnamed multipart/alternative (inline, 7-Bit, 0 bytes)
View raw message