Forum Discussion

larryx's avatar
larryx
Frequent Contributor
12 years ago

No load test result for large load test

Hello,
I ran 1k JMS messages load test (10 test steps, 100 threads) in SoapUI pro. however, I couldn't see any min/max/avg data from load test result table after I saw " LoadTest ended..." msg showed up in LoadTest Log. I tried couple small load test (i.e., 3 test steps, 6 threads) and the result data was fine. Anyone have seen the same problem?
Please Help Me!!
Larry

5 Replies

  • Hi Larry,

    Please give more insight into your tests such as how you are sending the 1K JMS message load test.

    Is it one test step (SOAP or REST?) that is sending the JMS messages?
    What load test strategy are you using, how many total runs do you have set?
    What version of SoapUI Pro are using?

    Please attach a screen shot of the load test table that is not giving any results. I can try to reproduce this locally to see if there is a general problem with doing large load tests for JMS messages.


    Regards,
    Marcus
    SmartBear Support
  • larryx's avatar
    larryx
    Frequent Contributor
    Hi Marcus,
    I will provide screen shot if I can reproduce the issue.
    It was JMS plain text messages sending/reading (SoapUI with groovy).
    Test Strategy: Burst
    Thread: 100
    Total runs: 100 (= threads?)
    SoapUI Pro 4.60
    Thanks,
    Larry
  • Hi,

    This post is similar to this one viewtopic.php?f=2&t=23502. Your doing a JMS load test using Groovy and high number threads. We do not support custom coding as this could be a code issue if using Groovy to read and send messages to the queue. However, I will do some more investigation to confirm.




    Regards,
    Marcus
    SmartBear Support
  • Hi Larry,

    I was able to do a load test using 100 threads and Burst strategy with total of 9 test steps. Three of the test steps were sending a message to the queue, and six were sending and receiving the message from the queue. All the data showed up in the load test, attaching screenshot. You could be having problems if your using Groovy to send and receive messes from the queue and your code is not thread safe.



    Regards,
    Marcus
    SmartBear Support
  • larryx's avatar
    larryx
    Frequent Contributor
    Hi Marcus,
    Thanks a lot for your research and screen shot.
    After I switched to 'Simple' strategy, the issue was gone. My code is not complicated. Not sure how can I figure out 'Not thread safe' portion in my code.
    Larry