Sebb, Thanks for the response.
Two reasons for doing it this way. First, built in constraints on the number of users that can authenticate concurrently causes some Jmeter threads to get failure results from the server. These threads then proceed to attempt the test requests that then also fail, corrupting the test. Second, the authentication sequence sometimes takes so long that it seriously biases the test results, even when all test requests are successful. Basically I'm trying to control for these two issues by only authenticating once. Bill -----Original Message----- From: sebb [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 13, 2005 4:36 PM To: JMeter Users List Subject: Re: Solution for Single Authenticator/Multiple Requestors? On 13/12/05, Bill Herndon <[EMAIL PROTECTED]> wrote: > All, > > I'm facing a situation where I need to test by having a single test > thread submit a set of three HTTP requests to do authentication to a > server (cookies-based) and then test with varying numbers of threads > that will submit requests for a specific duration. Has anybody ever > tried to set up such a scenario? Seems a very strange scenario. JMeter is intended to simulate multiple users; each thread simulates a different user. Can you not authenticate each thread separately? --------------------------------------------------------------------- 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]
