Well there is not tomcat in JMeter. My application runs on Tomcat, and Tomcat was not able to handle more than 200 users. So once I increased the Tomcat threads It is able to handle 200+ users at a time. After looking at exception , it appears that your JVM is running out of memory. Either increase the JVM memory or figure out which part of your test-plan is causing this issue. Listener can cause memory issue. If you using any listener then please disable that.
On Tue, Jul 2, 2013 at 8:34 PM, venkatpandiri [via JMeter] < [email protected]> wrote: > Is there a Tomcat in Jmeter application?**** > > I would greatly appreciate what kind of java settings I need to use for > running a test with 500 threads running continuously for 3 to 4 hours. This > is my first time testing with Jmeter.**** > > I would greatly appreciate it. For further test details please see my > previous email.**** > > Thank you very much for your fast response. **** > > *Have a good day.* > > * * > > *Regards,* > > *Venkat Pandiri* > > Sr Product Development Engineer**** > > *AT&T* - Digital Life, Innovative Services**** > > 754 Peachtree St, Atlanta, GA 30308**** > > office – 404.986.6444**** > > [hidden email] <http://user/SendEmail.jtp?type=node&node=5717350&i=0> **** > > [image: cid:[email protected]]**** > > ** ** > > *From:* [hidden > email]<http://user/SendEmail.jtp?type=node&node=5717350&i=1>[via JMeter] > [mailto: > ml-node+[hidden email]<http://user/SendEmail.jtp?type=node&node=5717350&i=2>] > > *Sent:* Tuesday, July 02, 2013 4:27 PM > *To:* PANDIRI, VENKATESHWARLU > *Subject:* Re: JMeter gets unstable after 200 threads.**** > > ** ** > > You can find the entire post here. > http://code4reference.com/2013/07/apache-debugging/**** > > ** ** > > I had changed the Tomcat configuration file and increased the number of > threads. **** > > ** ** > > I have already replied to you, Please check your email.**** > > ** ** > > On Tue, Jul 2, 2013 at 12:12 PM, venkatpandiri [via JMeter] <[hidden > email] <http://user/SendEmail.jtp?type=node&node=5717348&i=0>> wrote:**** > > Where did you change that setting on Jmeter side or your server can you > pleae let me know. Which file to edit and where the setting is > I am having trouble trying to run with 200 jmeter threads. > My test consists of 27 jdbc requets which call oracle stored procedures. > I am trying to run 200 threads with 27 thread groups. Each thread group > having about 7 or 8 threads. Ram up time of 1sec for each thread. I have > 500ms wait between each request for each thread group. > I am running on linux non gui mode. > using the below command. > nohup ./jmeter.sh -t POCOracleLoadTest_unix_parallel_single.jmx -n -l > sampleResults1.csv -j jmeterrun.log & > > I am running on a beefy linux server with 72GB ram and 32 cpus. I had > allocated 32 GB > > JVM_ARGS="-XX:MaxLiveObjectEvacuationRatio=50% -XX:-UseGCOverheadLimit > -XX:+HeapDumpOnOutOfMemoryError -Xms2048m -Xmx32768m > -Djava.security.egd=file:///dev/urandom" > > # Add Mac-specific property - should be ignored elsewhere (Bug 47064) > java $JVM_ARGS -Dapple.laf.useScreenMenuBar=true -jar `dirname > $0`/ApacheJMeter.jar "$@" > > Can you please advise how to do my jmeter and java settings so that I can > scale up and run it for 3 to 4 hours continously. > > I am getting the below errors: > 2013/07/02 11:44:53 ERROR - jmeter.threads.JMeterThread: Test failed! > java.lang.OutOfMemoryError: Java heap space > at > oracle.jdbc.driver.OraclePreparedStatement.setupBindBuffers(OraclePreparedStatement.java:2764) > > at > oracle.jdbc.driver.OraclePreparedStatement.processCompletedBindRow(OraclePreparedStatement.java:2202) > > at > oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3382) > > at > oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3488) > > at > oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:3857) > > at > oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1374) > > at > org.apache.jmeter.protocol.jdbc.AbstractJDBCTestElement.execute(AbstractJDBCTestElement.java:157) > > at > org.apache.jmeter.protocol.jdbc.sampler.JDBCSampler.sample(JDBCSampler.java:90) > **** > > at > org.apache.jmeter.threads.JMeterThread.process_sampler(JMeterThread.java:428) > > at > org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:256) > at java.lang.Thread.run(Thread.java:662) **** > > Thank you very much for anticiapted respose. > My email address is > [hidden email] <http://user/SendEmail.jtp?type=node&node=5717348&i=1> **** > > ------------------------------ > > *If you reply to this email, your message will be added to the discussion > below:* > > > http://jmeter.512774.n5.nabble.com/JMeter-gets-unstable-after-200-threads-tp5717269p5717347.html > **** > > To unsubscribe from JMeter gets unstable after 200 threads., click here. > NAML<http://jmeter.512774.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > **** > > ** ** > > Technical blog : code4reference <http://www.code4reference.com>**** > > LinkedIn : Rakesh Kumar<http://www.linkedin.com/pub/rakesh-kumar/17/1b1/632/> > **** > > ** ** > ------------------------------ > > *If you reply to this email, your message will be added to the discussion > below:* > > > http://jmeter.512774.n5.nabble.com/JMeter-gets-unstable-after-200-threads-tp5717269p5717348.html > **** > > To unsubscribe from JMeter gets unstable after 200 threads., click here. > NAML<http://jmeter.512774.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > **** > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://jmeter.512774.n5.nabble.com/JMeter-gets-unstable-after-200-threads-tp5717269p5717350.html > To unsubscribe from JMeter gets unstable after 200 threads., click > here<http://jmeter.512774.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5717269&code=aGFtZXBhbEBnbWFpbC5jb218NTcxNzI2OXwxNTI5MzcwMzY5> > . > NAML<http://jmeter.512774.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > ----- Technical blog : code4reference LinkedIn : Rakesh Kumar -- View this message in context: http://jmeter.512774.n5.nabble.com/JMeter-gets-unstable-after-200-threads-tp5717269p5717351.html Sent from the JMeter - User mailing list archive at Nabble.com.
