As of JMeter 4.0 underlying  FTPClient
<https://commons.apache.org/proper/commons-net/apidocs/org/apache/commons/net/ftp/FTPClient.html>
  
doesn't have any timeouts so if your server will never respond - your JMeter
test will never end. 

You can work it around by placing your FTP requests under the  Runtime
Controller
<http://jmeter.apache.org/usermanual/component_reference.html#Runtime_Controller>
  
- this way you will get confidence that your test will be terminated by the
Runtime Controller. 

Another option is switching from JMeter's FTP Request sampler to  JSR223
Sampler
<https://www.blazemeter.com/blog/load-testing-ftp-and-sftp-servers-using-jmeter>
  
where you will have full control over FTPClient instance and will be able to
define all the timeouts you can think of


>     FTPClient ftpClient = new FTPClient(x);
> 
>     ftpClient.setDefaultTimeout(x);
>     ftpClientp.setDataTimeout(x);
>     ftpClientp.setConnectTimeout(x);
>     ftpClient.setSoTimeout(x);
>     ftpClient.setControlKeepAliveTimeout(x);
>     ftpClient.setControlKeepAliveReplyTimeout(x);   





--
Sent from: http://www.jmeter-archive.org/JMeter-User-f512775.html

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to