Hi
you seem to have conflicting requirements. What you are simulating wont be
anything close to what the browser actually does (I believe IE doesn't send
more than 2 requests in parallel to any one domain). you are planning to
have the same session hit the server with multiple threads , which isnt the
workload of 500 users. Lets say each new User Session on the server has a
footprint of 1 MB then your test would only simulate a memory usage of 1Mb
not 500 MB
> (2) I want to simulate a workload of 500 users but do not want to create
500 actual test login accounts.
Unless there is a license issue or something , dont have this restriction.
In any case the only way I can think of is have two thread groups. Configure
your test plan to run your thread groups serially. Login in the first thread
group , extract session id, use beanshell to set this as a Jmeter Property
(not variable)
In the next thread group write your test for n Threads and use the session
id from the property
So
Test Plan (Check Run Thread Groups Consecutively)
Thread Group 1
Login Request
RegEx Extractor for session Id
Bean Shell listener to set session id as property (read the
variable and set it using the props object)
Thread Group 2
Test (Pass session id reading it from property)
${__property(sessionid)}
Ive never tested this btw...
regards
deepak
On Wed, May 20, 2009 at 8:06 AM, Nguyen Dao <[email protected]> wrote:
> Hi everyone,
>
> *DESCRIPTION OF MY SITUATION:*
>
> (1) The application I am testing is session-sensitive; I can not log in the
> second time using the same user as the first time without expiring the
> first
> time's session.
>
> (2) I want to simulate a workload of 500 users but do not want to create
> 500
> actual test login accounts.
>
> (3) I am currently using the "CSV Data Set Config" for obtaining login
> account for each thread.
>
> (4) I am also using the "Regular Expression Extractor" to extract the
> jsessionid from the URL for subsequent request.
>
> *QUESTION:*
> **
> (1) How can I set up my test plan to login only once under a ThreadGroup,
> and share the session with all threads? I have attempted to use the "Once
> Only Controller" to include the login request, but results shows that
> JMeter
> sends it for every thread. In other words, the scope of "Once Only
> Controller" seems to be within the Thread, rather than the ThreadGroup. Or
> perhaps, I am doing something wrong.
>
> (2) If possible, can you provide a high level skeleton for the test plan?
> For example:
> ThreadGroup
> -- Once Only Controller
> ----Login Requests
> ...
> ...
> etc.
>
> Thank you,
> Nguyen
> [email protected]
>
