On 15/09/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Thanks Sebb for your response. I have put my answers in colored text for
your perusal. Can you please have a look into them and clarify my doubts?
I'm afraid the colour does not show up here. Best to use prefixing, as I did...
> Guys,
> I want to know a basic Jmeter thing. I have parameterized my
> requests using Regular expression extractors meaning I am picking up
> values from earlier responses and then substituting them on subsequent
> requests. When I am running a few threads the parameter values are
getting
> replaced as expected.But sometimes it is so happening that under heavy
> load , the requests are not getting the parameter values substituted
> meaning that previous responses didn't respond with proper values.
Are you providing a default value for the RE?
I haven't provided with any default value as that is not going to serve my
purpose. The value that will be substituted is always going to be dynamic.
Having a default is useful for checking whether the RE worked or not;
otherwise the previous value of the variable (if any) will be left
behind when there is no match.
Try adding a default; it might help show why the problem is occurring.
If so, is the variable set to the default value, or is the variable
not even set?
Didn't check it because of the earlier reason.
But is there any value, or does the variable show up as ${variable} ?
The RE extractor won't be run if the sampler did not provide a sample
result (but that should not happen for time-outs, only for unhandled
errors)
I didn't understand this. What time out are u talking of here ? Is it
server time out ?can you please elaborate on it perhaps giving an example?
Sample timeout caused by waiting for the server to respond - this will
be shown as a failed sample.
e.g. try http://www.anything.invalid/ and you will get a timeout,
though this is caused by the name resolution process.
I'm not sure if there is any timeout on waiting for a server to reply
once it has been contacted OK - but if there is, it should be shown as
a failed sample.
I've just noticed that the code exits without doing anything if the
response data length is zero. I think that is a bug, as the RE
extractor can be applied to headers as well as the body...
Perhaps that is not happening as I have verified it with View Results tree
listener.I have checked that for a particular thread,one response is
totally blank,meaning that when i check the response by clicking on the
Show text radio button in the Response pane i see nothing. Subsequently
Jmeter has also send the next request which was to get its parameter
values substituted from the previous response and since the response is
blank, the parameters are not getting substituted.
If the response is empty, at present the RE extractor won't get run.
> Now my question is does Jmeter always wait for the response to render
and then
> only it sends the subsequent requests?
JMeter waits for a response (or time-out if appropriate) before
continuing.
> What happens if there is a stuck
> thread (response not rendered)at the server?
JMeter waits.
> Or if the delay period is
> reached then it bangs the server with a new request irrespective of
> whether or not previous responses were rendered?
>
Say that i have a timer at the thread group level and the period is say
1000 ms. Now if to a particular request , there is no response within that
period, will Jmeter send the next request(the next request is dependent on
the reponse of the previous request) ?I didn't understand the connotation
of time out here .
Timers are nothing to do with timeouts. Timers cause the thread to
pause for a while.
If a timeout occurs, JMeter will continue with the next sample.
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]
