>> We are using JMeter 2.3.0 and java 1.5. We are not using any assertions >> or pre or post processors. >> >> Also we are not using the SOAP request sampler. It did not matched with >> our performance testing requirement, so we have customized the Java >> request sampler to invoke web service request.
s> Are you sure that is not the cause of the problem? I am with sebb. Check the following scenarios: * Try to start plan with 1,2,3,4 threads and to measure how memory usage is changed. * Try to test your JMeter with disabled JavaRequest/or replace it with test.JavaRequest. * Try to start your JavaRequest sampler outside JMeter and observe memory usage. I think your JavaRequest is a reason of OutOfMemory error. Can you give me an answer to the following question: What kind of memory JMeter exceeded (Heap Memory, PermGen space)? Maybe you can find this information at the console or jmeter.log. s> JMeter can normally handle many more than 4 threads. s> For example on my 1GB system I'm currently running a 200 thread Java s> Request test which is generating over 2000 samples/second. Admittedly s> the is no IO involved. A test using the HTTP sampler against a local s> Tomcat shows similar capablilities (200 threads, over 2000 s> samples/second) on the same system. >> Regards, >> Ragini Thakur >> >> >> -----Original Message----- >> From: sebb [mailto:[EMAIL PROTECTED] >> Sent: Wednesday, January 09, 2008 5:29 PM >> To: JMeter Users List >> Subject: Re: Re[2]: JMeter goes Out of Memory >> >> Which version of JMeter ? Java? >> And which samplers do you use? >> >> Do you use lots of Assertions, Pre or Post-Processors? >> >> >> On 09/01/2008, Dmitry Kudrenko <[EMAIL PROTECTED]> wrote: >> > DK> Greetings, Ragini. >> > >> > Sorry, I skipped your messages about 4 users test. It is strange. >> > What OS do you use? >> > What memory usage do you have in the task manager? >> > Try to inspect JMeter with some profiler tool (JConsole or YourKit >> > Java Profiler, etc). >> > >> > What kind of memory JMeter exceeded (Heap Memory, PermGen space)? >> > >> > DK> How many threads do you start for your test plan? >> > DK> What kind of OutOfMememory Exception do you have? >> > >> > DK> Look to the following article if it is >> "java.lang.OutOfMemoryError: >> > DK> unable to create new native thread" exception: >> > >> > DK> http://www.egilh.com/blog/archive/2006/06/09/2811.aspx >> > >> > DK> Note about interesting paradox: >> > DK> "the more memory you give to the JVM the more likely you are to >> get >> > DK> java.lang.OutOfMemoryError: unable to create new native thread" >> (c) >> > >> > DK> Try to execute test plans on the several JMeter servers. It should >> > DK> help you. >> > >> > >> > RT>> We are using JMeter for Performance testing of one of the >> critical >> > RT>> application. We are using JMeter for testing Web service calls. >> > >> > RT>> When we execute the test with 4 users, the Jmeter goes out of >> memory and >> > RT>> we can not proceed with the test runs. >> > >> > RT>> >> > >> > RT>> We are not using any memory intensive listeners in out test plan. >> We are >> > RT>> using simple data writer. >> > >> > RT>> >> > >> > RT>> The configurations in our Jmeter.bat files are as follows: >> > >> > RT>> >> > >> > RT>> rem See the unix startup file for the rationale of the following >> > RT>> parameters, >> > >> > RT>> rem including some tuning recommendations >> > >> > RT>> set HEAP=-Xms512m -Xmx512m >> > >> > RT>> set NEW=-XX:NewSize=128m -XX:MaxNewSize=128m >> > >> > RT>> set SURVIVOR=-XX:SurvivorRatio=8 -XX:TargetSurvivorRatio=50% >> > >> > RT>> set TENURING=-XX:MaxTenuringThreshold=2 >> > >> > RT>> set EVACUATION=-XX:MaxLiveObjectEvacuationRatio=40% >> > >> > RT>> set RMIGC=-Dsun.rmi.dgc.client.gcInterval=600000 >> > RT>> -Dsun.rmi.dgc.server.gcInterval=600000 >> > >> > RT>> set PERM=-XX:PermSize=256m -XX:MaxPermSize=256m >> > >> > RT>> set DEBUG=-verbose:gc -XX:+PrintTenuringDistribution >> > >> > RT>> >> > >> > RT>> JMeter machine configuration: >> > >> > RT>> >> > >> > RT>> 32 bit processor and 1.88GHz , 2 CPU and 4GB RAM >> > >> > RT>> >> > >> > RT>> Application server configuration: >> > >> > RT>> >> > >> > RT>> 64 bit processor, 2 CPU and 8GB RAM >> > >> > RT>> >> > >> > RT>> We also tried changing the heap size to 1024m but, after that >> when we >> > RT>> run the Jmeter we get the error as JVM could not be initialized. >> > >> > RT>> >> > >> > RT>> Please suggest how we can solve this problem. >> > >> > RT>> -- Regards, Dmitry Kudrenko ARDAS group http://ardas.dp.ua --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
