Here is some info of the system running JMeter:
Windows Server 2003
Physical RAM : 4GB (available RAM > 3GB)
I have made a very simple test plan to test with both JMeter 2.2 and 2.3RC3
Test Plan
|-- Thread Group ( Number of Threads: 3000, Ramp-Up Period: 1000, Loop
Count: 1 )
|-- HTTP Cookie Manager
|-- HTTP Request ( Server Name: www.apache.org, Method: GET, Path: / )
|-- Summary Report
The limit I set in jmeter.bat without introducing OutOfMemoryError is as
follows:
set HEAP=-Xms1072m -Xmx1072m
set NEW=-XX:NewSize=384m -XX:MaxNewSize=384m
If I set the HEAP a few Meg higher, the JMeter console would display error
in less than 2 sec after the test starts.
Exception in thread "Thread-3" java.lang.OutOfMemoryError: unable to create
new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:574)
at
org.apache.jmeter.engine.StandardJMeterEngine.run(StandardJMeterEngine.java:400)
at java.lang.Thread.run(Thread.java:595)
I wonder why JMeter has such a limit even though the available physical RAM
is plenty.
It will take less than 5 minutes to set up the test if you would like to
investigate further.
Please advise. Thanks.
Jada
--
View this message in context:
http://www.nabble.com/OutOfMemoryError-tf4348833.html#a12445760
Sent from the JMeter - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
