Hi,
we have a situation where we need the user parameters to always be applied in a
group (which I thought was actually the default behaviour?).
Example:
We have two parameters that need to be managed as a pair: user.id and
resource.file
The user.id defines which user logs into the system being tested.
The resource.file is a list of records that this user will be able to access.
So for Jmeter "User_1" user.id=A has resource.file= 1.csv etc...
The resource files are distributed on the slaves and accessible to the jmeter
processes on those hosts.
Each jmeter slave has a distinct set of data (so no two slaves have the same
content in 1.csv), but all of the content in 1.csv is valid for user A and
_only_ for user A (the same applies for other users and data files).
The test does the following:
1. login (using ${user.id} from the user parameters)
2. loop
2.1 find a record (using
${_StringFromFile(${resource.path}/${resource.file})})
2.2 open the record
At 2.2 we are getting a lot of errors effectively saying record not found.
When we analysed this by looking at the requests being made we found that in
all of the errors User A would be trying to open a record which is NOT listed
in 1.csv! (The same applied to other users and file)
This error even occurs sometimes when we are running a single thread (no
slaves, 1 thread)!
Can anyone provide any clue as to why this is occurring?
Or how to ensure that all of the parameters for a given user are always past to
a particular thread?
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]
