You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by "hamepal@gmail.com" <ha...@gmail.com> on 2013/06/28 20:35:29 UTC
JMeter gets unstable after 200 threads.
I have one test plan which uses 13 HTTP samplers and one Regular Expression
extractor which extracts some value from the previous HTTP sampler. This
value is used in some of the HTTP sampler.
When I use 200 threads JMeter works fine but when I increase the threads
count it gets unstable and sometime it is not able to evaluate the variables
value and pass the variable name as value(e.g $MY_VAR). When my application
sees such data it complains and some how the connection remains open(Apache
Server status shows that)
I am using "HTTP Request Defauls" and setting connect and response timeout
values. But I don't see much difference.
Any idea what's going wrong ?
Thank you,
-----
Technical blog : code4reference
LinkedIn : Rakesh Kumar
--
View this message in context: http://jmeter.512774.n5.nabble.com/JMeter-gets-unstable-after-200-threads-tp5717269.html
Sent from the JMeter - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
For additional commands, e-mail: user-help@jmeter.apache.org
Re: JMeter gets unstable after 200 threads.
Posted by "hamepal@gmail.com" <ha...@gmail.com>.
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] <
ml-node+s512774n5717350h86@n5.nabble.com> 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:image001.png@01CC3B03.7FD4E0A0]****
>
> ** **
>
> *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.
Re: JMeter gets unstable after 200 threads.
Posted by "hamepal@gmail.com" <ha...@gmail.com>.
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] <
ml-node+s512774n5717347h93@n5.nabble.com> 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
> vp1515@att.com
>
> ------------------------------
> 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<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-tp5717269p5717348.html
Sent from the JMeter - User mailing list archive at Nabble.com.
Re: JMeter gets unstable after 200 threads.
Posted by hame <ha...@gmail.com>.
Sorry for my ignorance. I have figured out the problem, I had increased the
Apache Server thread but the problem persisted. But when I increased the
Tomcat thread value from 200 to 400 it worked fine.
On Sat, Jun 29, 2013 at 10:30 PM, Deepak Goel <de...@gmail.com> wrote:
> Hey
>
> Looks like your infrastructure is creaking for more resources, mostly
> more memory & processors and the threads hang then.
>
> Deepak
>
> On 6/29/13, Deepak Shetty <sh...@gmail.com> wrote:
> > so your tests are timing out right?
> > typically if you have a sequence of httpsamplers that need the previous
> > sampler(s) to succeed for them to work and you dont want these samplers
> to
> > show up as errors in your report (if the previous one failed) do
> something
> > like
> >
> http://theworkaholic.blogspot.com/2009/11/dependent-tests-in-jmeter-kind-of.html
> >
> >
> > On Fri, Jun 28, 2013 at 12:06 PM, hame <ha...@gmail.com> wrote:
> >
> >> Thanks Deepak.
> >>
> >> I checked in the jmeter.log and I found this.
> >>
> >> jmeter.extractor.RegexExtractor: RegexExtractor processing result
> >> 2013/06/28 12:01:59 DEBUG - jmeter.extractor.RegexExtractor: Regex =
> >> \"id\":([0-9]+)
> >> 2013/06/28 12:01:59 DEBUG - jmeter.extractor.RegexExtractor: Input =
> >> java.net.SocketTimeoutException: Read timed out
> >> at java.net.SocketInputStream.socketRead0(Native Method)
> >> at java.net.SocketInputStream.read(SocketInputStream.java:129)
> >> at
> java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
> >> at
> java.io.BufferedInputStream.read(BufferedInputStream.java:237)
> >> at
> >> org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:78)
> >> at
> >> org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:106)
> >> at
> >>
> >>
> org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1116)
> >> at
> >>
> >>
> org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1973)
> >> at
> >>
> >>
> org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1735)
> >> at
> >>
> >>
> org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1098)
> >> at
> >>
> >>
> org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
> >> at
> >>
> >>
> org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
> >> at
> >>
> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
> >> at
> >>
> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
> >> at
> >>
> >>
> org.apache.jmeter.protocol.http.sampler.HTTPHC3Impl.sample(HTTPHC3Impl.java:258)
> >> at
> >>
> >>
> org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.sample(HTTPSamplerProxy.java:62)
> >> at
> >>
> >>
> org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1088)
> >> at
> >>
> >>
> org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1077)
> >> 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)
> >>
> >>
> >>
> >> Looks like there is socketTimeoutException and Regular expression is not
> >> evaluated. Now I got some lead to investigate.
> >>
> >>
> >>
> >> On Fri, Jun 28, 2013 at 11:49 AM, Deepak Shetty <sh...@gmail.com>
> >> wrote:
> >>
> >> > check jmeter.log if there are errors(like memory issues) -
> >> > it however is more likely that it is your application that is
> >> > misbehaving
> >> > and you dont have suitable assertions that are catching
> errors/problems
> >> > (because of which your variables dont get set correctly)
> >> > By default JMeter will only recognise HTTP errors - so for e,g, if
> your
> >> > application returns a nice error page with status of 200 JMeter wont
> >> > know
> >> > there has been a problem (though things like your regular expression
> >> > extractors will not be able to verify the value you extract)
> >> > In your example where is MY_VAR being set - did you verify the
> response
> >> by
> >> > adding suitable assertions?
> >> >
> >> >
> >> > On Fri, Jun 28, 2013 at 11:35 AM, hamepal@gmail.com <
> hamepal@gmail.com
> >> > >wrote:
> >> >
> >> > > I have one test plan which uses 13 HTTP samplers and one Regular
> >> > Expression
> >> > > extractor which extracts some value from the previous HTTP sampler.
> >> This
> >> > > value is used in some of the HTTP sampler.
> >> > > When I use 200 threads JMeter works fine but when I increase the
> >> threads
> >> > > count it gets unstable and sometime it is not able to evaluate the
> >> > > variables
> >> > > value and pass the variable name as value(e.g $MY_VAR). When my
> >> > application
> >> > > sees such data it complains and some how the connection remains
> >> > open(Apache
> >> > > Server status shows that)
> >> > > I am using "HTTP Request Defauls" and setting connect and response
> >> > timeout
> >> > > values. But I don't see much difference.
> >> > >
> >> > > Any idea what's going wrong ?
> >> > >
> >> > >
> >> > > Thank you,
> >> > >
> >> > >
> >> > >
> >> > > -----
> >> > > Technical blog : code4reference
> >> > > LinkedIn : Rakesh Kumar
> >> > > --
> >> > > View this message in context:
> >> > >
> >> >
> >>
> http://jmeter.512774.n5.nabble.com/JMeter-gets-unstable-after-200-threads-tp5717269.html
> >> > > Sent from the JMeter - User mailing list archive at Nabble.com.
> >> > >
> >> > >
> ---------------------------------------------------------------------
> >> > > To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> >> > > For additional commands, e-mail: user-help@jmeter.apache.org
> >> > >
> >> > >
> >> >
> >>
> >
>
>
> --
> Namaskara~Nalama~Guten Tag~Bonjour
>
>
> --
> Keigu
>
> Deepak
> 7350012833
> deicool@gmail.com
> http://www.simtree.net
>
> Skype: thumsupdeicool
> Google talk: deicool
> Blog: http://loveandfearless.wordpress.com
> Facebook: http://www.facebook.com/deicool
>
> "Contribute to the world, environment and more :
> http://www.gridrepublic.org
> "
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> For additional commands, e-mail: user-help@jmeter.apache.org
>
>
Re: JMeter gets unstable after 200 threads.
Posted by Deepak Goel <de...@gmail.com>.
Hey
Looks like your infrastructure is creaking for more resources, mostly
more memory & processors and the threads hang then.
Deepak
On 6/29/13, Deepak Shetty <sh...@gmail.com> wrote:
> so your tests are timing out right?
> typically if you have a sequence of httpsamplers that need the previous
> sampler(s) to succeed for them to work and you dont want these samplers to
> show up as errors in your report (if the previous one failed) do something
> like
> http://theworkaholic.blogspot.com/2009/11/dependent-tests-in-jmeter-kind-of.html
>
>
> On Fri, Jun 28, 2013 at 12:06 PM, hame <ha...@gmail.com> wrote:
>
>> Thanks Deepak.
>>
>> I checked in the jmeter.log and I found this.
>>
>> jmeter.extractor.RegexExtractor: RegexExtractor processing result
>> 2013/06/28 12:01:59 DEBUG - jmeter.extractor.RegexExtractor: Regex =
>> \"id\":([0-9]+)
>> 2013/06/28 12:01:59 DEBUG - jmeter.extractor.RegexExtractor: Input =
>> java.net.SocketTimeoutException: Read timed out
>> at java.net.SocketInputStream.socketRead0(Native Method)
>> at java.net.SocketInputStream.read(SocketInputStream.java:129)
>> at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
>> at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
>> at
>> org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:78)
>> at
>> org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:106)
>> at
>>
>> org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1116)
>> at
>>
>> org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1973)
>> at
>>
>> org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1735)
>> at
>>
>> org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1098)
>> at
>>
>> org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
>> at
>>
>> org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
>> at
>> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
>> at
>> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
>> at
>>
>> org.apache.jmeter.protocol.http.sampler.HTTPHC3Impl.sample(HTTPHC3Impl.java:258)
>> at
>>
>> org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.sample(HTTPSamplerProxy.java:62)
>> at
>>
>> org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1088)
>> at
>>
>> org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1077)
>> 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)
>>
>>
>>
>> Looks like there is socketTimeoutException and Regular expression is not
>> evaluated. Now I got some lead to investigate.
>>
>>
>>
>> On Fri, Jun 28, 2013 at 11:49 AM, Deepak Shetty <sh...@gmail.com>
>> wrote:
>>
>> > check jmeter.log if there are errors(like memory issues) -
>> > it however is more likely that it is your application that is
>> > misbehaving
>> > and you dont have suitable assertions that are catching errors/problems
>> > (because of which your variables dont get set correctly)
>> > By default JMeter will only recognise HTTP errors - so for e,g, if your
>> > application returns a nice error page with status of 200 JMeter wont
>> > know
>> > there has been a problem (though things like your regular expression
>> > extractors will not be able to verify the value you extract)
>> > In your example where is MY_VAR being set - did you verify the response
>> by
>> > adding suitable assertions?
>> >
>> >
>> > On Fri, Jun 28, 2013 at 11:35 AM, hamepal@gmail.com <hamepal@gmail.com
>> > >wrote:
>> >
>> > > I have one test plan which uses 13 HTTP samplers and one Regular
>> > Expression
>> > > extractor which extracts some value from the previous HTTP sampler.
>> This
>> > > value is used in some of the HTTP sampler.
>> > > When I use 200 threads JMeter works fine but when I increase the
>> threads
>> > > count it gets unstable and sometime it is not able to evaluate the
>> > > variables
>> > > value and pass the variable name as value(e.g $MY_VAR). When my
>> > application
>> > > sees such data it complains and some how the connection remains
>> > open(Apache
>> > > Server status shows that)
>> > > I am using "HTTP Request Defauls" and setting connect and response
>> > timeout
>> > > values. But I don't see much difference.
>> > >
>> > > Any idea what's going wrong ?
>> > >
>> > >
>> > > Thank you,
>> > >
>> > >
>> > >
>> > > -----
>> > > Technical blog : code4reference
>> > > LinkedIn : Rakesh Kumar
>> > > --
>> > > View this message in context:
>> > >
>> >
>> http://jmeter.512774.n5.nabble.com/JMeter-gets-unstable-after-200-threads-tp5717269.html
>> > > Sent from the JMeter - User mailing list archive at Nabble.com.
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
>> > > For additional commands, e-mail: user-help@jmeter.apache.org
>> > >
>> > >
>> >
>>
>
--
Namaskara~Nalama~Guten Tag~Bonjour
--
Keigu
Deepak
7350012833
deicool@gmail.com
http://www.simtree.net
Skype: thumsupdeicool
Google talk: deicool
Blog: http://loveandfearless.wordpress.com
Facebook: http://www.facebook.com/deicool
"Contribute to the world, environment and more : http://www.gridrepublic.org
"
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
For additional commands, e-mail: user-help@jmeter.apache.org
Re: JMeter gets unstable after 200 threads.
Posted by Deepak Shetty <sh...@gmail.com>.
so your tests are timing out right?
typically if you have a sequence of httpsamplers that need the previous
sampler(s) to succeed for them to work and you dont want these samplers to
show up as errors in your report (if the previous one failed) do something
like
http://theworkaholic.blogspot.com/2009/11/dependent-tests-in-jmeter-kind-of.html
On Fri, Jun 28, 2013 at 12:06 PM, hame <ha...@gmail.com> wrote:
> Thanks Deepak.
>
> I checked in the jmeter.log and I found this.
>
> jmeter.extractor.RegexExtractor: RegexExtractor processing result
> 2013/06/28 12:01:59 DEBUG - jmeter.extractor.RegexExtractor: Regex =
> \"id\":([0-9]+)
> 2013/06/28 12:01:59 DEBUG - jmeter.extractor.RegexExtractor: Input =
> java.net.SocketTimeoutException: Read timed out
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(SocketInputStream.java:129)
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
> at
> org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:78)
> at
> org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:106)
> at
>
> org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1116)
> at
>
> org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1973)
> at
>
> org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1735)
> at
>
> org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1098)
> at
>
> org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
> at
>
> org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
> at
> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
> at
> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
> at
>
> org.apache.jmeter.protocol.http.sampler.HTTPHC3Impl.sample(HTTPHC3Impl.java:258)
> at
>
> org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.sample(HTTPSamplerProxy.java:62)
> at
>
> org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1088)
> at
>
> org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1077)
> 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)
>
>
>
> Looks like there is socketTimeoutException and Regular expression is not
> evaluated. Now I got some lead to investigate.
>
>
>
> On Fri, Jun 28, 2013 at 11:49 AM, Deepak Shetty <sh...@gmail.com> wrote:
>
> > check jmeter.log if there are errors(like memory issues) -
> > it however is more likely that it is your application that is misbehaving
> > and you dont have suitable assertions that are catching errors/problems
> > (because of which your variables dont get set correctly)
> > By default JMeter will only recognise HTTP errors - so for e,g, if your
> > application returns a nice error page with status of 200 JMeter wont know
> > there has been a problem (though things like your regular expression
> > extractors will not be able to verify the value you extract)
> > In your example where is MY_VAR being set - did you verify the response
> by
> > adding suitable assertions?
> >
> >
> > On Fri, Jun 28, 2013 at 11:35 AM, hamepal@gmail.com <hamepal@gmail.com
> > >wrote:
> >
> > > I have one test plan which uses 13 HTTP samplers and one Regular
> > Expression
> > > extractor which extracts some value from the previous HTTP sampler.
> This
> > > value is used in some of the HTTP sampler.
> > > When I use 200 threads JMeter works fine but when I increase the
> threads
> > > count it gets unstable and sometime it is not able to evaluate the
> > > variables
> > > value and pass the variable name as value(e.g $MY_VAR). When my
> > application
> > > sees such data it complains and some how the connection remains
> > open(Apache
> > > Server status shows that)
> > > I am using "HTTP Request Defauls" and setting connect and response
> > timeout
> > > values. But I don't see much difference.
> > >
> > > Any idea what's going wrong ?
> > >
> > >
> > > Thank you,
> > >
> > >
> > >
> > > -----
> > > Technical blog : code4reference
> > > LinkedIn : Rakesh Kumar
> > > --
> > > View this message in context:
> > >
> >
> http://jmeter.512774.n5.nabble.com/JMeter-gets-unstable-after-200-threads-tp5717269.html
> > > Sent from the JMeter - User mailing list archive at Nabble.com.
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> > > For additional commands, e-mail: user-help@jmeter.apache.org
> > >
> > >
> >
>
Re: JMeter gets unstable after 200 threads.
Posted by hame <ha...@gmail.com>.
Thanks Deepak.
I checked in the jmeter.log and I found this.
jmeter.extractor.RegexExtractor: RegexExtractor processing result
2013/06/28 12:01:59 DEBUG - jmeter.extractor.RegexExtractor: Regex =
\"id\":([0-9]+)
2013/06/28 12:01:59 DEBUG - jmeter.extractor.RegexExtractor: Input =
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
at
org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:78)
at
org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:106)
at
org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1116)
at
org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1973)
at
org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1735)
at
org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1098)
at
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
at
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
at
org.apache.jmeter.protocol.http.sampler.HTTPHC3Impl.sample(HTTPHC3Impl.java:258)
at
org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.sample(HTTPSamplerProxy.java:62)
at
org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1088)
at
org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1077)
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)
Looks like there is socketTimeoutException and Regular expression is not
evaluated. Now I got some lead to investigate.
On Fri, Jun 28, 2013 at 11:49 AM, Deepak Shetty <sh...@gmail.com> wrote:
> check jmeter.log if there are errors(like memory issues) -
> it however is more likely that it is your application that is misbehaving
> and you dont have suitable assertions that are catching errors/problems
> (because of which your variables dont get set correctly)
> By default JMeter will only recognise HTTP errors - so for e,g, if your
> application returns a nice error page with status of 200 JMeter wont know
> there has been a problem (though things like your regular expression
> extractors will not be able to verify the value you extract)
> In your example where is MY_VAR being set - did you verify the response by
> adding suitable assertions?
>
>
> On Fri, Jun 28, 2013 at 11:35 AM, hamepal@gmail.com <hamepal@gmail.com
> >wrote:
>
> > I have one test plan which uses 13 HTTP samplers and one Regular
> Expression
> > extractor which extracts some value from the previous HTTP sampler. This
> > value is used in some of the HTTP sampler.
> > When I use 200 threads JMeter works fine but when I increase the threads
> > count it gets unstable and sometime it is not able to evaluate the
> > variables
> > value and pass the variable name as value(e.g $MY_VAR). When my
> application
> > sees such data it complains and some how the connection remains
> open(Apache
> > Server status shows that)
> > I am using "HTTP Request Defauls" and setting connect and response
> timeout
> > values. But I don't see much difference.
> >
> > Any idea what's going wrong ?
> >
> >
> > Thank you,
> >
> >
> >
> > -----
> > Technical blog : code4reference
> > LinkedIn : Rakesh Kumar
> > --
> > View this message in context:
> >
> http://jmeter.512774.n5.nabble.com/JMeter-gets-unstable-after-200-threads-tp5717269.html
> > Sent from the JMeter - User mailing list archive at Nabble.com.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> > For additional commands, e-mail: user-help@jmeter.apache.org
> >
> >
>
Re: JMeter gets unstable after 200 threads.
Posted by Deepak Shetty <sh...@gmail.com>.
check jmeter.log if there are errors(like memory issues) -
it however is more likely that it is your application that is misbehaving
and you dont have suitable assertions that are catching errors/problems
(because of which your variables dont get set correctly)
By default JMeter will only recognise HTTP errors - so for e,g, if your
application returns a nice error page with status of 200 JMeter wont know
there has been a problem (though things like your regular expression
extractors will not be able to verify the value you extract)
In your example where is MY_VAR being set - did you verify the response by
adding suitable assertions?
On Fri, Jun 28, 2013 at 11:35 AM, hamepal@gmail.com <ha...@gmail.com>wrote:
> I have one test plan which uses 13 HTTP samplers and one Regular Expression
> extractor which extracts some value from the previous HTTP sampler. This
> value is used in some of the HTTP sampler.
> When I use 200 threads JMeter works fine but when I increase the threads
> count it gets unstable and sometime it is not able to evaluate the
> variables
> value and pass the variable name as value(e.g $MY_VAR). When my application
> sees such data it complains and some how the connection remains open(Apache
> Server status shows that)
> I am using "HTTP Request Defauls" and setting connect and response timeout
> values. But I don't see much difference.
>
> Any idea what's going wrong ?
>
>
> Thank you,
>
>
>
> -----
> Technical blog : code4reference
> LinkedIn : Rakesh Kumar
> --
> View this message in context:
> http://jmeter.512774.n5.nabble.com/JMeter-gets-unstable-after-200-threads-tp5717269.html
> Sent from the JMeter - User mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> For additional commands, e-mail: user-help@jmeter.apache.org
>
>