Guys, its working (crudely) using IP Aliases approach. I used HTTPRequestHTTPClient and used the Source IP address field. I have to create Multiple thread group and for every thread group, I used the source IP intended. There are number of issues with this approach.
- I have to create thread group for every user - Scalability issues. This will work for me as of now because I have <50 user load to be created. In the meantime, I will also explore Grinder as suggested. The reason for mapping Ip to session is - We want to identify the unique 'siteid' from where user is loggin in. i.e on loading the http://<ip>/app the form asks for username/password. So along with username/password, The browser should also send the 'siteid' but this information shouldn't be filled by user. We used Gears initially, but that caused deployment problems. So Ip address to 'siteid' mapping is created. This has its limitations.. DHCP, Dynamic NAT, PAT etc. Vikas Gupta Software/QA Lead Cisco Health Solutions [email protected] (epage) Think before you print. This e-mail may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply e-mail and delete all copies of this message. -----Original Message----- From: Sudip Kumar Bhattacharya [mailto:[email protected]] Sent: Tuesday, July 20, 2010 1:02 PM To: JMeter Users List Subject: Re: unique Source IP Address Vikas, I also agree that using unique ips is not the right way to identify unique users. Think of the scenario when multiple people from some company try to access ur site via a proxy server. U wud see the same source ip on all the requests and that wud be the proxy server ip. Are you saying that your application will not allow them to login? Sent on my BlackBerry® from Vodafone -----Original Message----- From: chaitanya bhatt <[email protected]> Date: Tue, 20 Jul 2010 00:55:29 To: JMeter Users List<[email protected]> Reply-To: "JMeter Users List" <[email protected]> Subject: Re: unique Source IP Address @Kirk: You are right. I guess the author of this thread should consider "Grinder" for load testing. It supports IP spoofing and its equally user friendly. -Chaitanya M Bhatt http://www.performancecompetence.com 2010/7/20 Kirk <[email protected]> > you can setup aliases.. however, I doubt that you're going to get enough > aliases to get a decent load test. I question why you're equating a session > to an IP address. Not saying you shouldn't, just it's unusual. > > Regards, > Kirk > > On Jul 20, 2010, at 5:17 AM, Vikas Gupta (vikgupt2) wrote: > > > I couldn't quite understand the meaning of "Source IP Address" usage . > The official doc says > > > > Source IP address: > > [Only for HTTP Request HTTPClient] Override the default local IP address > for this sample. The JMeter host must have multiple IP addresses (i.e. IP > aliases or network interfaces). If the property httpclient.localaddress is > defined, that is used for all HttpClient requests. > > > > "The Jmeter host must have multiple IP addresses" .. what exactly does > this sentence mean ? Does it mean that the Jmeter host should have multiple > NIC's and every NIC has a unique IP address. In that case I cannot have as > many NIC's as the number of users I want to simulate. > > > > This is confusing me. > > > > Vikas Gupta > > > > > > -----Original Message----- > > From: Sudip Kumar Bhattacharya [mailto:[email protected]] > > Sent: Monday, July 19, 2010 5:37 PM > > To: JMeter Users List > > Subject: Re: unique Source IP Address > > > > Ya, I agree. > > Try using the http client. That has a source ip option. Load it from a > csv file. > > Let us know if that works. > > Sent on my BlackBerry® from Vodafone > > > > -----Original Message----- > > From: "Vikas Gupta (vikgupt2)" <[email protected]> > > Date: Mon, 19 Jul 2010 14:02:31 > > To: JMeter Users List<[email protected]> > > Reply-To: "JMeter Users List" <[email protected]> > > Subject: RE: unique Source IP Address > > > > That will be worst case scenario.. I have to run multiple instances of > Jmeter on VM's, then again it won't be a feasible model for 1000 user > thread. > > > > Hopefully we can find some other solution. > > > > > > Vikas Gupta > > Software/QA Lead Cisco Health Solutions > > > > > > > > > > Think before you print. > > This e-mail may contain confidential and privileged material for the sole > use of the intended recipient. Any review, use, distribution or disclosure > by others is strictly prohibited. If you are not the intended recipient (or > authorized to receive for the recipient), please contact the sender by reply > e-mail and delete all copies of this message. > > > > > > > > > > -----Original Message----- > > From: Sudip Kumar Bhattacharya [mailto:[email protected]] > > Sent: Monday, July 19, 2010 5:19 PM > > To: JMeter Users List > > Subject: Re: unique Source IP Address > > > > Run a distributed jmeter test. But even then u will need as many jmeter > servers as ur users. > > Not sure what wud be the best way to emulate your use case. > > Sent on my BlackBerry® from Vodafone > > > > -----Original Message----- > > From: "Vikas Gupta (vikgupt2)" <[email protected]> > > Date: Mon, 19 Jul 2010 13:22:09 > > To: <[email protected]> > > Reply-To: "JMeter Users List" <[email protected]> > > Subject: unique Source IP Address > > > > Hi All, > > > > > > > > IS it possible to have unique source IP address for every user thread > > HTTPS traffic in Jmeter ? > > > > > > > > The portal server under test maps unique IP address to unique user, > > hence this requirement. > > > > > > > > Looking forward to reply. > > > > > > > > Thanks & Regards > > > > > > > > Vikas Gupta > > > > > > > > > > > > Vikas Gupta > > Software/QA Lead Cisco Health Solutions > > > > [email protected] <mailto:[email protected]> (epage) > > <mailto:[email protected]> > > > > > > > > Think before you print. > > > > This e-mail may contain confidential and privileged material for the > > sole use of the intended recipient. Any review, use, distribution or > > disclosure by others is strictly prohibited. If you are not the intended > > recipient (or authorized to receive for the recipient), please contact > > the sender by reply e-mail and delete all copies of this message. > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > 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] > > > > > --------------------------------------------------------------------- > 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]
