On 14/06/06, Bennett McElwee <[EMAIL PROTECTED]> wrote:
I started this "concurrent requests" thread a while ago. I have just
created a separate bug report in Bugzilla, and it just occurred to me
that the bug would explain the "concurrent requests" problem too.
ASF Bugzilla Bug 39808 "Invalid redirect causes incorrect sample time"
points out that if a server returns a redirect to an invalid URL, then
JMeter erroneously doubles the time for that sample. In my case, here's
what happens:
1. JMeter sends a request to the server.
2. The server queues the request.
3. After 3 minutes, the server (under load) gives up and tries to
redirect to an error page. Sadly, due to misconfiguration, it redirects
to the invalid URL "http://HOST:PORT/error.html";
4. JMeter gets the redirect and records the time as 3 minutes.
5. JMeter tries to parse the redirect URL and creates an error result
(time: 3 minutes) since the URL is invalid.
6. Here's the bug: JMeter somehow includes the error result twice in the
overall result. It adds up the times, so the final result shows as 6
minutes even though it should be only 3.
It seems to generate two identical sub-samples, which are then added together.
Only the parent sample is shown in CSV output files; in XML output
files the second sample is shown as:
<httpSample reference="../httpSample"/>
which probably means that the same sample has been added to the parent twice.
7. My test reports go haywire.
Since affected samples will appear to have started earlier that they
actually did, this would create the appearance of overlapping samples.
Yes, it could well do so.
I'm pretty sure that's what happened here. As sebb suspected, the
problem was with the sample durations, not the sample end times.
So we will have a nice feeling of closure on this problem once Bug 39808
is fixed. Hooray!
Thanks for solving the mystery...
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
