Re: Analysing the View Result Tree Listener
Hi,
your problem is you are not signing in to your application
You should add an assertion to the 'sign in' sampler to check the user has
actually signed in
for example is the 'sign out' link there after the user signs in?
Also...
some of your variables have not been set :
VIEWSTATE = ${viewState}
You should check your Regular Expressions are correct
I would advise adding a Debug Sampler to the end of your test script and
checking your values there (within the View Results Tree)
ZK
--
View this message in context:
http://jmeter.512774.n5.nabble.com/Analysing-the-View-Result-Tree-Listener-tp5713858p5724416.html
Sent from the JMeter - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
For additional commands, e-mail: user-h...@jmeter.apache.org
Re: Analysing the View Result Tree Listener
http://jmeter.apache.org/usermanual/best-practices.html Tree listener is for debug , never ever use it for a load test with lot of users or itérations . Regards Philippe On Friday, July 6, 2012, Dzmitry_Kashlach wrote: How much users do you need to simulate? You can try our JMeter testing cloud, http://blazemeter.com, it can give you up to 18000 users. -- View this message in context: http://jmeter.512774.n5.nabble.com/Analysing-the-View-Result-Tree-Listener-tp5713858p5713901.html Sent from the JMeter - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org javascript:; For additional commands, e-mail: user-h...@jmeter.apache.orgjavascript:; -- Cordialement. Philippe Mouawad.
Re: Analysing the View Result Tree Listener
hi, 1st thing I notice is you are not using any assertions on your HTTP request However; this doesn't explain your issue, but I would advise you do add a response assertion How many threads are you running? Do you get this issue with just 1 thread? or do you have a higher load? (I personally do not go higher than 300 threads per load injector, I also limit each thread group to 1 request per second) If this issue doesn't happen with 1 thread but a greater load then the 1st place I would check would be your application logs HTH ZK -- View this message in context: http://jmeter.512774.n5.nabble.com/Analysing-the-View-Result-Tree-Listener-tp5713858p5713859.html Sent from the JMeter - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org For additional commands, e-mail: user-h...@jmeter.apache.org
RE: Analysing the View Result Tree Listener
My experience with the View Results Tree listener suggest that using it has a big affect on the performance characteristics of the test. I noticed 2 things: 1) The test generally runs slower when the View Results Tree listener is collecting sample results. (I attribute that to the fact that it is having to write all that data to disk). 2) When you reach a certain point (several thousand samples), the test responses are substantially altered by the View Results Tree listener (filling up some buffer somewhere?)... I would suggest that you use the View Results Tree with some caveats: 1) Don't use it for a load-test, or performance-test scenario, it will interfere with the accuracy of your results. 2) Use it for 'Errors' recording only (in load/perf tests), since it will log only the responses that had an error (this is really helpful in debugging what broke). 3) Use other listeners for tracking the performance and load of your system (the perfmon listener is handy, and summary results is useful too). -- Robin D. Wilson Sr. Director of Web Development KingsIsle Entertainment, Inc. VOICE: 512-777-1861 www.KingsIsle.com -Original Message- From: ZK [mailto:stevesenio...@gmail.com] Sent: Thursday, July 05, 2012 9:37 AM To: jmeter-u...@jakarta.apache.org Subject: Re: Analysing the View Result Tree Listener Hi, if I were you, I would run the test several times, each time with a higher load start with 100 threads, then the next test 200 and so on After each test look at your Average response times in the Aggregate Report You may notice after a certain load these average response times become unacceptably high thus causing a timeout Also does your application have any timeout value set? you may be able to correlate these 2 points Another point would be if you are getting issues with say 500 threads, try distributed testing, i.e use 2 load injectors with each running 250 threads each and see if the issue still occurs HTH ZK -- View this message in context: http://jmeter.512774.n5.nabble.com/Analysing-the-View-Result-Tree-Listener-tp5713858p5713886.html Sent from the JMeter - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org For additional commands, e-mail: user-h...@jmeter.apache.org - To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org For additional commands, e-mail: user-h...@jmeter.apache.org
