Forum Discussion

TNeuschwanger's avatar
TNeuschwanger
Community Leader
18 years ago

loadtestrunner -h parameter causes connection failure

SoapUI 2.0.1

I can run a load test from within SoapUI just fine.  However, when running the same load test and calling it via loadtestrunner with a -h parameter, it will always produce a "connection timedout" failure for the first request it encounters within the load test. It therefore never gets past the first request step for the duration of the test.

So... If I issue this command line (attempting to override the loadtest thread count), it will fail:
loadtestrunner.bat -s"TestSuite MXP Load" -c"TestCase MXP" -l"LoadTest UTM Simple" -h2 -f"H:\Results Performance" -r "H:\Performance-soapui-project.xml"

By just removing the -h parameter the following command line works fine and completes the load test successfully:
loadtestrunner.bat -s"TestSuite MXP Load" -c"TestCase MXP" -l"LoadTest UTM Simple" -f"H:\Results Performance" -r "H:\Performance-soapui-project.xml"

It is an easy enough work-around to just enter the desired thread within SoapUI then use the command line as needed but that cramps my automation efficiency. 

Thank you for such a great tool at a great price.  Regards.
  • omatzura's avatar
    omatzura
    Super Contributor
    18 years ago
    Hi!

    the -h option is used to change the host, maybe you meant to use the -m option to change the limit?

    regards!

    /Ole
    eviware.com
  • TNeuschwanger's avatar
    TNeuschwanger
    Community Leader
    18 years ago
    Thank you for quick reply.

    I am getting some conflicting information on the -h option then...  When launching the loadtestrunner without any parameters to see the available options, it indicates -h as thread override (listed below).  Today's online userguide for SoapUILoadTestRunner lists two different meanings for the -h parameter...

    Additionally, when the -h parameter is included, loadtestrunner acts as if it is overriding the thread count by supplying the following message in the run log (within the user interface the thread count is 5, using -h1 overrides it to 1)
    ...
    16:18:40,985 INFO  [SoapUIProLoadTestRunner] Overriding threadCount [5] with specified [1]
    Progress: 1 - Creating Virtual User 1
    Progress: 1 - Started thread 1
    ...

    C:\Program Files\eviware\soapUI-Pro-2.0.1\bin>loadtestrunner
    soapUI 2.0.1 Pro LoadTest Runner
    usage: loadtestrunner [options]
    -t    Sets the soapui-settings.xml file to use
    -c    Sets the testcase
    -d    Sets the domain
    -e    Sets the endpoint
    -f    Sets the output folder to export to
    -h    Overrides the LoadTest ThreadCount
    -l    Sets the loadtest
    -m    Overrides the LoadTest Limit
    -p    Sets the password
    -r    Exports statistics and testlogs for each LoadTest run
    -s    Sets the testsuite
    -u    Sets the username
    -w    Sets the WSS password type, either 'Text' or 'Digest'
    Missing soapUI project file..


    Regards.
  • omatzura's avatar
    omatzura
    Super Contributor
    18 years ago
    Hi!

    duh.. thanks.. this is a bug in the LoadTestRunner, it should have been "n" for the threadcount change; will be fixed in the upcoming 2.0.2 release..

    sorry for the inconvenience!

    regards,

    /Ole
    eviware.com