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] > >
