If you do not understand what URL rewriting is or how session ids are used by web applications, remove the URL rewriting modifier, remove the regex extractor you have added for session id and ONLY use the Cookie Manager. If you have recorded the script and the jsessionid is in url because of that , delete that too . All your requests should NOT have any session ids. Also verify that you have follow redirects (and not redirect automatically) for every request. Then in your login request verify that all parameters using request tab are exactly the same as browser(ignore session id). If it still fails send your browser trace for the initial and login request along with the request response data from JMeter.
regards deepak On Mon, Mar 22, 2010 at 12:04 AM, Rajesh Tiwary <[email protected]> wrote: > > Hi deepak, > > well in the response data tab for tree listener i am not getting any error > message..also all the reports in tree listener are showing error count:0 > but the problem is aftering sending the usid and password i m still getting > the login page in the response data.. > > compairing the results with LiveHttpHeaders and jmeter request i found that > the request for login page is simewhat different in both the cases.. > > in Jmeter the cookie data for JSESSIONID is = suppose 7213989182 > > then the in the request url a different cookie data is getting attached.. > like../abcd/Login.do;jsessionid=A81164C14C0AA45564F423798B5D7440 {note > different cookie data for jsessionid} > > but in LiveHTTPHeaders the cookie data for jsessionid and the value of > jsessionid attached with the url are both same,,. > > now my concern is that whether due to this problem i m getting redirected > to > the login page or what.. > > also m using following parameters in regular expression but that is not > working .. > > ref name: xyz > regular expression=JSESSIONID=(.+?)' > template:$1$ > match:1 > default value: not found > > so after using this when i am calling the regular expression in the url as > Login.do;jsessionid=${xyz} > m getting the result as Login.do;jsessionid=not found > > ..so what shall i do now..shall i record with badboy the requests..or how > can i extract the value of JSESSIONID from the cookie and attach it to the > url.. > > note m not getting anyerror as all signals are green > > > > > > > > Deepak Shetty wrote: > > > > Hi > > First using a browser trace tool like liveHttpHeaders for FF figure out > if > > your app is using cookies or not for managing sessionids . If yes , > remove > > the URL rewriting modifier that you have. Next inspect the response that > > you > > get from the login request in View Results Tree Listener (see the text or > > render as html). If your application gives you good error messages you > > might > > be able to see the failure , if not compare the data from the request tab > > with the data that you can see for the login request in LiveHttpHeaders > > and > > see where the mismatch is > > > > regards > > deepak > > > > On Thu, Mar 18, 2010 at 10:32 PM, Rajesh Tiwary <[email protected]> > wrote: > > > >> > >> Hi deepak, > >> > >> Thanks for replying.. > >> > >> i have checked the check box called follow redirect. > >> no i am not getting the confirmation page..probably theres a problem > with > >> sending correct session id.. > >> can you tell me whats the procedure to apply correlation properly? > >> > >> Thanks > >> rajesh > >> > >> > >> Deepak Shetty wrote: > >> > > >> > Hi > >> > been discussed multiple times in these forums in various forms, > >> typically > >> > you have Reedirect Automatically instead of follow redirects or your > >> login > >> > didnt succeed or you didnt send back the correct session id . Your > test > >> > also > >> > has a URL Rewriting Modifier and a cookie manager , you normally need > >> only > >> > 1 > >> > of the two. > >> > > >> > After login you have a view results tree listener and you have the > >> > following > >> > statement "so i should get the confirmation page here..as i think." > >> > Do you get it or not? If you dont then your login hasnt worked , if > you > >> > did > >> > then the problem is the session id is not being passed as the > >> application > >> > expects. > >> > > >> > Ways to diagnose this problem are described here > >> > http://wiki.apache.org/jakarta-jmeter/DifferentBehaviour > >> > > >> > On Wed, Mar 17, 2010 at 10:14 PM, Rajesh Tiwary <[email protected]> > >> wrote: > >> > > >> >> > >> >> Hi, > >> >> > >> >> i am testing a HTTPS web application using JMeter.,where i am facing > >> an > >> >> issue of getting a session expired message. > >> >> > >> >> i am using JMeter 2.3.4 r800132. > >> >> > >> >> My aim is to record following sequence for the HTTPS application: > >> >> > >> >> Index page------>Login Page------->confirmation page,button click to > >> get > >> >> a > >> >> form---->add detail in the form---->and search detail by entering > data > >> in > >> >> the text field of the page after successful addition of the detail in > >> the > >> >> form. > >> >> > >> >> now i am able to record the page sequence. > >> >> > >> >> and this is my test plan.. > >> >> > >> >> --THREAD GROUP > >> >> ---HTTP COOKIE MANAGER > >> >> ---HTTP URL RE-WRITING MODIFIER > >> >> ---SIMPLE CONTROLLER(For index page) > >> >> ...(various HTTP request recorded) > >> >> ---TREE LISTENER (Response data showing page loaded successfully) > >> >> > >> >> ---SIMPLE CONTROLLER(For login page) > >> >> ...(various HTTP request recorded) > >> >> ---TREE LISTENER (Response data showing login page loaded > >> >> successfully,but in the above http request i have sent the userid and > >> >> password ..so i should get the confirmation page here..as i think..) > >> >> > >> >> > >> >> ---SIMPLE CONTROLLER(For confirmation page,button click to get form) > >> >> ...(various HTTP request recorded,which include button click) > >> >> ---TREE LISTENER (Response data showing YOUR SESSION > EXPIRED,Kindly > >> >> Re-login..) > >> >> > >> >> and same result for further steps... > >> >> > >> >> Can anyone suggest me solution for this problem?? > >> >> > >> >> regards, > >> >> > >> >> rajesh > >> >> -- > >> >> View this message in context: > >> >> > >> > http://old.nabble.com/Getting-Session-Expired-Message-for-the-load-test-of-a-HTTPS-web-application-using-JMeter-tp27941766p27941766.html > >> >> Sent from the JMeter - User mailing list archive at Nabble.com. > >> >> > >> >> > >> >> --------------------------------------------------------------------- > >> >> To unsubscribe, e-mail: [email protected] > >> >> For additional commands, e-mail: [email protected] > >> >> > >> >> > >> > > >> > > >> > >> -- > >> View this message in context: > >> > http://old.nabble.com/Getting-Session-Expired-Message-for-the-load-test-of-a-HTTPS-web-application-using-JMeter-tp27941766p27950899.html > >> Sent from the JMeter - User mailing list archive at Nabble.com. > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > > > > > > -- > View this message in context: > http://old.nabble.com/Getting-Session-Expired-Message-for-the-load-test-of-a-HTTPS-web-application-using-JMeter-tp27941766p27982933.html > Sent from the JMeter - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
