Mailing-List: contact jmeter-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "JMeter Users List" <jmeter-user@jakarta.apache.org>
Received-SPF: pass (nike.apache.org: domain of rylach@gmail.com designates
 209.85.218.209 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=lAednRrnbdrAYfzHG0pgjY9VKx5hNcKlUrvRl8XDg8fXOpQ5dLUOamudGoOym1S/rz
         P+/qphdlShkHJSGWxZt4SLVdn+xGD0u/JKFh4ZNlbLPhgV1xzRF2GhRbQRoKa0tu6I6w
         d6euYjlwgagBIWIkk5Mil8ogyq0gG7qeKyFtk=
MIME-Version: 1.0
Date: Tue, 1 Dec 2009 14:58:07 +0100
Message-ID: <c4b2cc120912010558k5669299bqac6218a352127a8a@mail.gmail.com>
Subject: Removing variables
From: =?ISO-8859-2?Q?Ryszard_=A3ach?= <rylach@gmail.com>
To: jmeter-user@jakarta.apache.org
Content-Type: multipart/alternative; boundary=00032555abdaceea5e0479ab25dc

--00032555abdaceea5e0479ab25dc
Content-Type: text/plain; charset=ISO-8859-1

I'm preparing a test profile using regexp and xpath extractors quite
extensively. Each matching extractor creates some variables local to thread
and if the thread is looping over the thread group, then there is a risk,
that variables from previous thread group run will be used in the next one.
Is there a smart way for avoiding this? I've tried to add beanshell sampler
at the and of profile removing those variables, but it is hard to maintain
with big profile. Is there a 'clear variables each iteration' checkbox
similar to that one for cookies?

Maybe changing testing strategy e.g. that way:

* add constant timer e.g.60 000 ms to the profile
* set big amount of threads (10000)
* set long ramp-up period (3600 s)
* set thread group so, that every thread goes through it only once

What do you think about?

R.

-- 
"First they ignore you. Then they laugh at you. Then they
fight you. Then you win." - Mohandas Gandhi.

--00032555abdaceea5e0479ab25dc--