Contributions
Re: LoadTest runner runs out of 8 GB memory immediately
The issue is that loadtestRunner is running out of memory, while running the same load test from the SoapUI UI, does not. I am not sure why I should use loadUI when it works fine with the soapUI frontend. Seems like the issue seems to be in loadtest Runner. We are using loadtest runner so that we can run the tests from commandline.10 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.3KViews0likes0CommentsLoadTest runner runs out of 8 GB memory immediately
loadtestRunner runs out of memory immediately while running test from cmdline. The same test when run from SoapUIPro UI consumes about 1.5 GB at the most but when run from load test runner consumes 8 GB of allocated memory withing couple of minutes and then crash with outofMemory error. I have set up the loadtest based on your tutorial section as well. I tired running from command line both on 4.6.4 and 5.0 with the same result. I am attaching the loadtestRunner.bat file that I modified to give it 8 GB of RAM. Attaching the cmd line that I used call "C:\Program Files\SmartBear\SoapUI-Pro-5.0.0\bin"\loadtestrunner.bat -e${#Project#BASE_URL} -hitops-qa-153:8080 -s"PerPage" -c"PerPage" -l "PerPage Loadtest 25 User 25 per Sec" -r -FPDF -R"LoadTest Report" -fC:\tmp\LoadUI\PerPage_25_25_250 -Dsoapui.properties=C:\work\UIAlerts\LoadTest\soapui_perpage_250.properties Z:\svn\UIAlerts\main\alerts\alerts-it\src\test\resources\Alerts-edaa-PerPage-soapui-project.xml >> C:\tmp\LoadUI\1.out 2>> C:\tmp\LoadUI\2.out10 years agoPlace ReadyAPI QuestionsReadyAPI Questions2KViews0likes5CommentsRe: URIException error while running loadtestRunner from cmdline
The reason is that there are multiple requests from the load test run. I modified the load test script to run only one and I am attaching the results which is much smaller. The same test runs fine from the soapUI pro. The file response_UI is the response o/p from the soapUI pro UI and response_script is from the loadtestRunner.bat run. The file 1.out is the soapUI o/p and the file 2.out is the stack trace for the same run I did using the cmdline. I have the same number of users running for tests without JSON which are working fine and do not run out of memory. I did a diff on the response o/p and they are the same.11 years agoPlace ReadyAPI QuestionsReadyAPI Questions5.8KViews0likes0CommentsRe: URIException error while running loadtestRunner from cmdline
I am attaching the response I get during the run. I am also seeing that running at higher number of users causes the SoapUI to hog memory and then run out of memory. I had set 8 GB of memory for SoapUI.11 years agoPlace ReadyAPI QuestionsReadyAPI Questions5.8KViews0likes0CommentsURIException error while running loadtestRunner from cmdline
I am trying to set the properties from command line and run the loadtest using loadtestrunner.bat. But when I set the custom property by specifying the -D option, the run throws the follow stack trace and error. Here is the request that is sent out 13:26:40,497 DEBUG [SoapUIMultiThreadedHttpConnectionManager$SoapUIDefaultClientConnection] Sending request: GET /alerts-edaa/msa/alerts/types/ManagedAlert/instances?alt=json HTTP/1.1 and the error is nu.xom.MalformedURIException: Double slash (//) in path at nu.xom.Verifier.throwMalformedURIException(Verifier.java:161) at nu.xom.Verifier.checkPath(Verifier.java:396) at nu.xom.Verifier.checkAbsoluteURIReference(Verifier.java:907) at nu.xom.Element._setNamespaceURI(Element.java:869) at nu.xom.Element.setNamespaceURI(Element.java:852) at com.eviware.soapui.impl.rest.support.handlers.JsonXmlSerializer.processJSONObject(JsonXmlSerializer.java:1159) at com.eviware.soapui.impl.rest.support.handlers.JsonXmlSerializer.write(JsonXmlSerializer.java:721) at com.eviware.soapui.impl.rest.support.handlers.JsonXmlSerializer.write(JsonXmlSerializer.java:676) at com.eviware.soapui.impl.rest.support.handlers.JsonMediaTypeHandler.createXmlRepresentation(JsonMediaTypeHandler.java:55) at com.eviware.soapui.impl.wsdl.submit.transports.http.BaseHttpResponse.getContentAsXml(BaseHttpResponse.java:435) at com.eviware.soapui.impl.wsdl.teststeps.RestTestRequestStep.propertyChange(RestTestRequestStep.java:481) at java.beans.PropertyChangeSupport.fire(Unknown Source) at java.beans.PropertyChangeSupport.firePropertyChange(Unknown Source) at java.beans.PropertyChangeSupport.firePropertyChange(Unknown Source) at com.eviware.soapui.model.support.AbstractModelItem.notifyPropertyChanged(AbstractModelItem.java:85) at com.eviware.soapui.impl.support.AbstractHttpRequest.setResponse(AbstractHttpRequest.java:732) at com.eviware.soapui.impl.wsdl.teststeps.RestTestRequest.setResponse(RestTestRequest.java:138) at com.eviware.soapui.impl.wsdl.teststeps.RestTestRequestStep.run(RestTestRequestStep.java:922) at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.runTestStep(AbstractTestCaseRunner.java:235) at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner.runCurrentTestStep(WsdlTestCaseRunner.java:48) at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:148) at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:43) at com.eviware.soapui.impl.wsdl.support.AbstractTestRunner.run(AbstractTestRunner.java:135) at com.eviware.soapui.impl.wsdl.loadtest.WsdlLoadTestRunner$InternalTestCaseRunner.run(WsdlLoadTestRunner.java:544) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) This happens only when I send the query for json format. When I run the same test using the SoapUI gui, it runs fine without any errors. This is the command line I execute. call "C:\Program Files\SmartBear\SoapUI-Pro-4.6.4\bin"\loadtestrunner.bat -e${#Project#BASE_URL} -hitops-qa-153:8080 -s"Simple Instance Get" -c"Simple Instance GET" -l "Simple Get Loadtest 25 User 25 per Sec" -r -FPDF -R"LoadTest Report" -fC:\tmp\LoadUI\Get_JSON__25_25 -Dsoapui.properties=C:\work\UIAlerts\LoadTest\sopaui_json.properties Z:\svn\UIAlerts\main\alerts\alerts-it\src\test\resources\Alerts-edaa-Simple-Gets-soapui-project.xml >> c:\tmp\loadUI\1.out I set the custom propery based on the documentation @ http://www.soapui.org/Scripting-Propert ... rties.html Here is my properties file with a one line entry test.alt.property=json and I have the custom property value for alt set as ${test.alt.property}. I get the requests properly in the tomcat server and it seems to be returning 200. There were 746 requests sent by the loadtest and I have 749 stacks of the above error. Would this be related to the same issue discussed @ http://forum.soapui.org/viewtopic.php?f ... 52&p=54439 ? I am using SoapUI Pro 4.6.411 years agoPlace ReadyAPI QuestionsReadyAPI Questions7.4KViews0likes11CommentsRe: [Res]Running a specific loadtest strategy from command line
I think I solved the issue with writing to PDF. The -R value was wrong, and when I fixed that it worked. Now I will try running different test scenarios creating new load tests.11 years agoPlace ReadyAPI QuestionsReadyAPI Questions828Views0likes0Comments