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 <[email protected]> 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, [email protected] <[email protected]
> >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: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> >
>
