rebeccaM
13 years agoOccasional Contributor
Out of Memory Error calling SoapUI runner with 10/sec
I am using SoapUI (4.5.1) to call an internal WSDL for a WCF project running on my box. (We would change the URL to be on a test server down the road, but I am just playing with getting LoadUI working with the current version of our service).
I am using LoadUI 2.1.0. I just added a soapUI Runner, a Fixed Rate VU Generator, and a Table Log (although that doesn't matter, I get the problem with or without the log). SoapUI Runner has 2 test steps, one to set properties and one to do the soap request. This particular request passes back a lot of data, which is why I am using it as a test case - we wanted to stress test our service. If I am just running at 1 request per second, I get around 2400-3600 in the TimeTaken column in the Table Log.
When I bump up my Fixed Rate generator to 10/sec and let it run for a bit, after a while I get an Out Of Memory error in LoadUI. A reproducible way to get this is I let it run to about 100 requests and hit stop. While it finishes the queued requests, it runs out of memory. I had 119 requests, 98 running, 21 completed, 2 failed, 0 queued, 0 discarded in the soapUI Runner window.
Computer has 8 GB RAM, Windows 7 Pro 64 bit, Java 7.
I looked at this post, but I didn't see anything that would help. I didn't mess around with concurrent samples - they are just set to the default 100. All the advanced settings are set to the default.
Any ideas?
I am using LoadUI 2.1.0. I just added a soapUI Runner, a Fixed Rate VU Generator, and a Table Log (although that doesn't matter, I get the problem with or without the log). SoapUI Runner has 2 test steps, one to set properties and one to do the soap request. This particular request passes back a lot of data, which is why I am using it as a test case - we wanted to stress test our service. If I am just running at 1 request per second, I get around 2400-3600 in the TimeTaken column in the Table Log.
When I bump up my Fixed Rate generator to 10/sec and let it run for a bit, after a while I get an Out Of Memory error in LoadUI. A reproducible way to get this is I let it run to about 100 requests and hit stop. While it finishes the queued requests, it runs out of memory. I had 119 requests, 98 running, 21 completed, 2 failed, 0 queued, 0 discarded in the soapUI Runner window.
Computer has 8 GB RAM, Windows 7 Pro 64 bit, Java 7.
I looked at this post, but I didn't see anything that would help. I didn't mess around with concurrent samples - they are just set to the default 100. All the advanced settings are set to the default.
Any ideas?