I've got a Counter config element in my test that is configured to start at
1, increment by 1 to a maxiumu of 65516. When I run the test with 1 thread,
3 loops, 1 sec ramp-up the counter evaluates to 18, 25, then 32. Same test,
but 2 threads and I get 33, 49, 62 for thread 1 and 36, 50, 64 for thread 2.
A simplified view of the test plan:
HTTP Request Defaults
HTTP Header Manager
JDBC Login Defaults
Thread Group
HTTP Cookie Manager
Counter
Uniform Random Timer
Once Only Controller
Simple Controller
HTTP Request
HTTP Header Manager
Simple Controller
HTTP Request
HTTP Header Manager
JDBC Request
HTTP Request
HTTP Header Manager
I'm using the Counter Reference Name in the JDBC Request to pull test data
out of a database.
The actual test plan is more complex than this. If you need to see it let
me know and I'll e-mail it to you.
It's probably something to do with how the tree is setup as I have had a
simple tree were the counter works as expected. Any ideas on how I can get
this counter to go 1, 2, 3?
TIA,
Steve
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
