On 10 August 2010 13:56, SanderW <[email protected]> wrote: > > Hi, sorry for replying to an old message but i'm facing the same issues as > the topicstarter. > > Is there still no other way to stop processing after HTTP1 Request, than to > enclose the subsequent samplers in an If Controller? > > > My JMeter-script (version 2.3.4) consists of 15 Transaction Controllers > (with Generate parent sample switch on), each with multiple HTTP Requests. > If one of the HTTP Requests fails the iteration should abort and the > Transaction Controller should show a failed transaction in the summary > report. > > The Thread Group looks like this: > Number of Threads (users): 50 > Ramp-up Period = 300 > Loop Count = 10 > The 'Action to be taken after a Sampler' error is set to Continue. If I set > this to Stop thread at this point and one of the HTTP Requests fails then > the transaction will not show up in the summary report as failed nor is the > transaction shown in the Results Tree, which makes it difficult to see which > HTTP Request is failing.
That seems to be a bug - please raise a Bugzilla issue so it does not get forgotten. > After the Transaction Controller I added an If Controller that checks if the > last sample was ok. If the last sample is not OK a Test Action with Stop > Thread is called upon, but this causes the user to abort the script and not > execute the other look counts. > > -- > View this message in context: > http://jmeter.512774.n5.nabble.com/BeanShell-Assertion-Can-a-failed-assertion-force-the-next-iteration-of-a-loop-tp533789p2428605.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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
