hi,
you know, that in a high concurrent load test, something wrong might happen
which does not appear in single thread test/validation stage.
In such circumstance, I think error log will help. you can print some useful
error information for the threads which failed.
But I only know that 'View Results Tree' component can show what was happening
when executing. unfortunately the results are mixed when you run multiple
threads, so It's much not convinient to see what result is belonging to which
thread. Anyway, 'View Results Tree' must not be used in formal load test, for
that it consumes much cpu and memory resources...
Any advice?
