A loop count of 1 won't in general produce repeatable results. This is
more of a burst test, and the startup overheads are likely to be the
major factor in any timings.
Having said that, JMeter 2.2 includes the thread name in the View Tree
Listener (Sampler Result Pane) and the View Table Listener (Thread
Name column)
On 12/09/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi,
I am running a test with about 25 threads and a ramp up period of 25
seconds and loop count=1. Now my test configuration is such that when ever
there is an error in a particular thread that thread should stop. When I
run the test i see that out of 25 threads some 3-4 threads are stopping
intermittently because of some error. (Seen that from jmeter.log)Now
obviously I know which threads have stopped. But since I am using a View
Tree Listener i have no way to say which request belongs to which thread.
All through out my test i have used Regular expression extractors to parse
the response and put values dynamically into subsequent requests. My gut
feeling is that the threads are failing because responses werent parsed
correctly for a particular thread. Now is there any way to see which
requests belong to which thread?A the monent all the requests are coming
one after another and we cant differntiate between requests from different
threads.Also at the same time i would like to requests and responses like
i am able to do now through View results Tree listener.
Regards,
Subhrajyoti
Mobile: +919830079545
Mail: [EMAIL PROTECTED]
Web: www.labware.com
LabWare LIMS Solutions - Results Count
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
