Turns out this won't work for me - I need timed execution that isn't
dependent on the amount of time it takes for previous executions to
respond. Also, I can't run more jmeter instances - not enough resources!
I'll continue to use my thread pool jmeter patch. Thanks anyway.
Deepak Shetty wrote:
Hi
Clear the cookies (assuming you are using JSESSIONID in cookies) at the end
of the iteration (or use bsh). If your application is using urlrewriting
(the sessionid is part of the url) then for the first request in the loop,
use a url without the sessionid
another option is run multiple jmeter instances instead of jmeter master
slave --search the archives for related discussions
regards
deepak
On Tue, Sep 22, 2009 at 9:11 AM, Craig Flichel <[email protected]> wrote:
I have to test high-volume of users - over 20k.
JMeter creates/starts a thread for each of these even though many of them
are scheduled to execute after a very long delay. My jmeter slaves cannot
handle so many running threads.
An option that was presented to me was to have them looping and repeating
resetting the context between iterations, to avoid reuse of the tomcat
session on loop. How would I reset the context?
My test setup is simple - HTTP Cookie Manager, HTTP Request Defaults,
multiple HTTP Samplers.
---------------------------------------------------------------------
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]
