On 1 December 2011 04:48, iyerbalaji <[email protected]> wrote:
> Hi Team,
>
> I need to stress test an application.
>
> Application Description:
> •       The application serves the purpose of Secure File Transfer Management 
> and
> storage.
> •       It securely collects, stores, manages, and distributes the data.
> •       It’s hosted on IIS.
> •       The user can upload and download data to/from the application server.
> •       Various interfaces are used for end user to upload-download data from 
>  the
> server
> •       Interfaces use the following protocols to communicate between the 
> server
> and client machine
>        o    HTTP(S)
>        o    FTP over SSL(FTPS)
>        o    FTP over SSH(SFTP)
>
> The concern is to use Jmeter for file transfer using FTPS and SFTP.I have
> not been successful in transferring a file from my machine to the server
> using the ports 22(sftp) and 990(ftps).
> Following errors are displayed for sftp and ftps respectively:
>
> SFTP(22)
> " Response message: org.apache.commons.net.MalformedServerReplyException:
> Could not parse response code. "
> FTPS(990)
> " Response message: org.apache.commons.net.ftp.FTPConnectionClosedException:
> Connection closed without indication. "
>
> Appreciate your help in this regard.

Standard JMeter only supports the FTP sampler; merely changing the FTP
port will not change the protocol it uses.

I assume you must be using a 3rd-party FTP Sampler, in which case,
please ask the provider for advice.

>
> --
> View this message in context: 
> http://jmeter.512774.n5.nabble.com/Jmeter-support-for-FTPS-FTP-over-SSL-and-SFTP-FTP-over-SSH-tp5037601p5037601.html
> Sent from the JMeter - User mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>

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

Reply via email to