Forum Discussion

kamilineni's avatar
kamilineni
Occasional Contributor
13 years ago

[Resolved] Issues with load test

Hello Guys
I have too many issues running my load test. I am testing the web services. Well, let me explain my load test scenario.

I have created my soap UI scripts and the Data source for this script is XLS sheet and everything is working well in Soap UI. I need to run this test in a UNIX box from my windows computer (Distributed testing). So, I installed the Load UI agent in the UNIX box and also deployed my XLS sheet in the UNIX box and I can see the agent reading my XLS sheet. I have deployed my test case into the agent and started running the test. This is where I ran into problems. When I am running the load test, I don't see any of the requests completed or failed or discarded in soap UI runner. All the things I can see in the soap UI runner is "requests running" reaching 100 and thereafter they start queuing. And that too I can see the server is not really hit with the load I am generating, instead its getting the requests in a slower manner.

Another issue I am falling into is - The load UI agent is getting disconnected and reconnected from load UI during the test when I increase the load. My load UI agent is throwing this error. "Exception caught when calling on action handler for stop in multi ram".


And its running too slowly. I mean it’s not getting the data source file as expected. Instead it’s reading the file in a soap UI manner. I think its reading one row and after finishing it, it’s reading another row.

Please suggest something. I am very new to the tool.

Thanks,
Kumar

11 Replies

  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    13 years ago
    Howdy!

    kamilineni wrote:
    I have created my soap UI scripts and the Data source for this script is XLS sheet and everything is working well in Soap UI.

    Could you clarify this please? Are you using a Groovy Script TestStep to read an XLS sheet or are you using an Excel DataSource from soapUI Pro?

    Thanks

    Henrik
    SmartBear Software
  • kamilineni's avatar
    kamilineni
    Occasional Contributor
    13 years ago
    Yes,
    I am using Excel data source from SOAP UI PRO to read the data.

    Thanks,
    Kumar
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    13 years ago
    Hi again!

    Let's do things one step at a time and let us know where it fails:


    • Install loadUI 2.0 beta1.

    • Try if it works as a load test in soapUI Pro.

    • Try if it works in loadUI local mode.

    • Try if it works in loadUI distributed mode with an agent running on the same machine.


    Remember that the online documentation is always there to help you.

    Regards

    Henrik
    SmartBear Software
  • kamilineni's avatar
    kamilineni
    Occasional Contributor
    13 years ago
    I can't try with the Load UI Agent in the local mode as I don't have access to the server from my machine. Our assumption is that, The agent installed in the server machine has access to the server and I will have access only to the agent. So, I cant test with the agent in the local mode.

    Thanks,
    Kumar
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    13 years ago
    kamilineni wrote:
    I can't try with the Load UI Agent in the local mode as I don't have access to the server from my machine. Our assumption is that, The agent installed in the server machine has access to the server and I will have access only to the agent. So, I cant test with the agent in the local mode.

    Thanks,
    Kumar

    Ok, could you verify this assumption by doing a request from the agent machine using ping, wget or something similar?

    Requests can be running for up to 3 minutes before they time out. This is normal TCP behavior. Have you waited for that long after you've sent a request?

    Regards

    Henrik
    SmartBear Software
  • kamilineni's avatar
    kamilineni
    Occasional Contributor
    13 years ago
    I verified using Ping and I have access to the sever from the Agent. I have waited for 10 minutes after sebding the request and most of the times I am getting "Socket Time out Error".

    Thanks,
    Kumar
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    13 years ago
    kamilineni wrote:
    I have waited for 10 minutes after sebding the request and most of the times I am getting "Socket Time out Error".

    But... earlier you wrote this:
    kamilineni wrote:
    When I am running the load test, I don't see any of the requests completed or failed or discarded in soap UI runner.


    Please clarify if and where you are getting errors.

    Regards

    Henrik
    SmartBear Software
  • kamilineni's avatar
    kamilineni
    Occasional Contributor
    13 years ago
    Well,
    1) The socket out error is seen in the Agent log. I think I understood the socket out error. I am getting it when I am stopping the test. So, lets forget this.

    2) But, Looking at the Soup UI Runner in my local machine, I can see only requests running, and later all of them getting into queue. But, no request completed. I think may be something wrong with the scripts. I am attaching the picture of my scripts. Please look at them and help.


    Thanks,
    Kumar
  • kamilineni's avatar
    kamilineni
    Occasional Contributor
    13 years ago
    Henrik,

    I am able to run the Test in Load UI beta1. My agent is sending the request to the services upon starting the test. I can see in the agent log, that it is getting the response back from the services. But, I am not able to see that response in my local machine soap UI runner. And, also, I dont see any responses even in the statistic work bench. This is the issue I am facing.

    Thanks,
    Kumar
  • kamilineni's avatar
    kamilineni
    Occasional Contributor
    13 years ago
    Henrik,

    This problem is resolved and my tests are going good. It was resolved by removing the "Data Source Loop" at the end of my script. Thank you very much for your great support.

    Regards,
    Kumar