Thaks Sebb, By adding Cookie Manager at Controller level, my problem has been resolved.
~ Roopal Shah -----Original Message----- From: sebb [mailto:[EMAIL PROTECTED] Sent: Saturday, April 09, 2005 4:37 PM To: [EMAIL PROTECTED] Cc: JMeter Users List Subject: Re: Problem Implementing Test Plan due to Secured Page Access Logic The Cookie Manager automatically handles cookies sent by the server. There is no need to add any yourself. See: http://jakarta.apache.org/jmeter/usermanual/component_reference.html#HTTP_Co okie_Manager S. On Apr 9, 2005 5:01 AM, Roopal Shah <[EMAIL PROTECTED]> wrote: > Thanks Sebb, > > Yes, I have added a cookie manager to my test plan. But I have not added any > new cookie in the cookie manager. Do I have to add cookie manually or Does > JMeter automatically add new cookies? > > Thanks & Regards > ~ Roopal Shah > > -----Original Message----- > From: sebb [mailto:[EMAIL PROTECTED] > Sent: Friday, April 08, 2005 7:40 PM > To: JMeter Users List; [EMAIL PROTECTED] > Subject: Re: Problem Implementing Test Plan due to Secured Page Access > Logic > > Have you added a Cookie Manager to the test plan? > > On Apr 8, 2005 2:20 PM, Roopal Shah <[EMAIL PROTECTED]> wrote: > > Hi, > > We are experiencing a problem with creating a test plan in JMeter. We know > > the cause of the problem but need inputs/help to identify the approach for > > resolving the problem. > > The application that is being tested contains code logic that ensures that > > the application pages cannot be downloaded/requested without successful > > completion of the login validation process. This means that in order to > > perform any function within the application a user must have logged into > the > > application successfully. Once a user has logged into the application > > his/her user information is saved/cached into the HTTP Session. The > > application's JSP pages contain an include directive that invokes some > code > > logic which queries the HTTP Session to verify whether the user's > > information (user profile) is available in the session and based on this > > check it determines whether the user has logged into the system. > > The JMeter test plan is created/implemented as follows: (under single > Thread > > Group) > > * Make a request to the Login page (JSP Page) and pass the required > > parameters > > * Make a request to the application pages and pass the required > parameters > > We were expecting that JMeter should be able to maintain the user > > information in the HTTP Session when the application pages are requested > > because login validation is the first thing that happens when the test > plan > > is executed. However, based on our findings the test plan fails since the > > user information is not found when application pages are requested > > subsequent to completion of the login validation. > > I would greatly appreciate any assistance / pointers that can help me > > resolve the above mentioned issue. > > Thanks and Regards, > > Roopal Shah > > > > --- > > Outgoing mail is certified Virus Free. > > Checked by AVG anti-virus system (http://www.grisoft.com). > > Version: 6.0.801 / Virus Database: 544 - Release Date: 11/24/2004 > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --- > Incoming mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.801 / Virus Database: 544 - Release Date: 11/24/2004 > > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.801 / Virus Database: 544 - Release Date: 11/24/2004 > > --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.801 / Virus Database: 544 - Release Date: 11/24/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.801 / Virus Database: 544 - Release Date: 11/24/2004 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
