The JMeter code is synchronised where it saves the variables. Also, the set of variables is chosen using threadNum % varCount, so a given thread will always get the same set.
I don't see how the variables can get out of step unless some other test element is updating one of the values. I suggest creating a Bugzilla issue and attaching the JMX file. Redact any sensitive information first. On 21 July 2010 15:43, Jörg Godau <[email protected]> wrote: >> What about "Update once per iteration" - is that selected or not? > > Not selected. > > >> And where is the User Parameter Pre-Processor in the test plan? >> Is it in scope of multiple samplers? > > Sorry I'm not sure I understand the question. I've provided a screenshot of > our test plan in the "testplan.png" attachment. Does that help or do you need > some other information? > > >> Remember that Pre-Processors are processed before every sample that is >> in scope. > > ?? > >> Are the same number of entries (non-empty columns) present for all >> parameter names (rows)? > > There are two rows, each row has 6 columns (plus name), and each cell > contains valid values. > > > >> Which version of JMeter? > > 2.4 r961953 > > > > > Mit freundlichen Grüßen > Jörg Godau > > SCHÜTZE Consulting Informationssysteme GmbH Argentinische Allee 22b > 14163 Berlin > Tel.: 030/ 802 49 44 > Fax: 030/ 8090 39 95 > www.schuetze-berlin.de > > Geschäftsführer: Klaus-Dieter Schütze > Registergericht: Amtsgericht Charlottenburg > Registernummer: HRB 73618 > Umsatzsteuer-Identifikationsnummer gemäß § 27a Umsatzsteuergesetz: DE > 813181239 > > > > --------------------------------------------------------------------- > 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]
