I am not using session or cookies at all in my application right now. So I guess adding cookie listener doesn't make any sense to be added to JMeter test case. I shall use cookies later and shall add cookie listener to test my application. I don't want to store any data in web server so will not use sessions, rather shall store userid in cookie and fetch users data from memcache from cache machine based on the cookie.
-- Rajeev Sharma Sr. Software Engineer Yahoo! Inc -----Original Message----- From: Dave Newton <newton.d...@yahoo.com> Reply-to: "Struts Users Mailing List" <user@struts.apache.org> To: Struts Users Mailing List <user@struts.apache.org> Subject: Re: [SOLVED]: Need to disable session interceptor Date: Tue, 01 Sep 2009 16:10:28 -0400 Peter Phillips wrote: >>From Rajeev's earlier emails: > > "I am developing an application which does not need to use sessions at all." > "I opened some pages on my application and found there was one session > created for my browser and others for other clients, So I guess this > has nothing to do with JMeter. Sessions are being created for every > client." > > Therefore I think adding page session="false" is the correct solution > in his case and he has no need for the cookie listener in JMeter as no > cookies will be created! While I did misunderstand the original post, my statement still stands--if you want the JMeter tests to run as a real client would, the tests need to emulate the client. Unless every user has cookies disabled then the tests won't (necessarily) run the same way. Dave --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
