jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitry Kudrenko <>
Subject Re[2]: JMeter goes Out of Memory
Date Wed, 09 Jan 2008 09:50:46 GMT
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> 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>> We are not using any memory intensive listeners in out test plan. We are
RT>> using simple data writer.


RT>> The configurations in our Jmeter.bat files are as follows:


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>> JMeter machine configuration:


RT>> 32 bit processor and  1.88GHz , 2 CPU and 4GB RAM 


RT>> Application server configuration:


RT>> 64 bit processor, 2 CPU and 8GB RAM 


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>> Please suggest how we can solve this problem.


RT>> Regards,
RT>> Ragini Thakur

Dmitry Kudrenko
ARDAS group

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message