These are all HTTPSamplers.
I have elements like this for each step
<elementProp name="" elementType="HTTPArgument">
<boolProp
name="HTTPArgument.always_encode">false</boolProp>
<stringProp
name="Argument.name">eventSource</stringProp>
<stringProp
name="Argument.value">${Step5Action}</stringProp>
<stringProp name="Argument.metadata">=</stringProp>
<boolProp name="HTTPArgument.use_equals">true</boolProp>
</elementProp>
I have RE extractor for each step
<RegexExtractor guiclass="RegexExtractorGui" testclass="RegexExtractor"
testname="Regular Expression Extractor" enabled="true">
<stringProp
name="RegexExtractor.useHeaders">false</stringProp>
<stringProp
name="RegexExtractor.refname">Step5Action</stringProp>
<stringProp name="RegexExtractor.regex">button
smokeId="Next"
onclick="Events.invokeEvent\('([^']+)', true\)"
class="button"</stringProp>
<stringProp name="RegexExtractor.template">$1$</stringProp>
<stringProp name="RegexExtractor.default"></stringProp>
<stringProp name="RegexExtractor.match_number">1</stringProp>
</RegexExtractor>
Rest of the elements in each step are elements like
<elementProp name="" elementType="HTTPArgument">
<boolProp
name="HTTPArgument.always_encode">false</boolProp>
<stringProp name="Argument.name">${Country}</stringProp>
<stringProp name="Argument.value">US</stringProp>
<stringProp name="Argument.metadata">=</stringProp>
<boolProp name="HTTPArgument.use_equals">true</boolProp>
</elementProp>
I am not using any conditional logic.
======================
1. I recorded the script using proxy recorder.
2. I replaced eventSource in each sampler with a value I get from a RE,
since the values are dynamically generated.
3. Even for rest of the elements I use RE to fill in appropriate values.
==============================================
Yes you are right it does not make sense, why in the world will page go
to 4th step when it is supposed to be on 6th step. Intrestingly when I
do it manually it is impossible in the application to go to 4th step
after the 5th step is completed.
Thanks
Modha/-
-----Original Message-----
From: sebb [mailto:[EMAIL PROTECTED]
Sent: Friday, November 16, 2007 6:54 AM
To: JMeter Users List
Subject: Re: Sleepless in Phoenix ( 2 thread issue)
On 16/11/2007, Modha Khammammettu <[EMAIL PROTECTED]> wrote:
> Hi All
>
> I have a test with 13 steps (I have 300ms constant timer, View Result
> Tree).
What are the steps? HTTP samplers, LDAP ?
> When I run this with 1 thread it runs perfectly, even if I have it
> running forever.
>
> Interesting things happens when I start it with 2 or more threads.
>
> When it is supposed to be on the 6th step, it will show step4 and then
> rest of all steps fail. It always does that (even if I run with 5
> threads) till 5th step it runs perfectly and then next step I expect
> it to be on step6 it is on step4.
This does not make sense.
> Here is the interesting part. When I run with 2 threads:
> Only Thread Name: Thread Group 1-1 has this problem Thread Name:
> Thread Group 1-2 go through 13 steps without issue forever.
>
> I don't know why it runs fine with 1 thread and when I run with 2
> threads ( runs fine in one thread group and fails in other) . That too
> failure always start at Step5.
What are these steps?
Are you using any conditional logic?
If or While or Switch?
> Any ideas how to debug.....
The Java Request sampler is useful for generating samples without
needing a server.
But without a bit more detail of what the test contains, it's difficult
to advise.
But please don't post the JMX to the list.
> Thanks
> Modha/-
>
---------------------------------------------------------------------
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]
