Hi there, Thanks for the reply. I am using the cookie manager. It seems the jsession is sent in a cookie immediately before the log in page. The user logs in with jusername and jpassword, -- this is where I would expect to see Jmeter reference this jsession ** it does not **.
If you view the same flow under a different proxy such as fiddler, or httpwatch you see the cookie being sent in the header. Its not sent in the header in Jmeter or at all for that matter. I tried recording different ways just to see if maybe the orginal recording was off, but that was not the case. If Jmeter even saw the session id in the cookie then I could regex and send it in the outgoing header. Outside of this I'm not sure what to do since Jmeter doesnt seem to see the cookie at all. Also to confuse things further 1 user with 25 loops works fine. 5 users with 5 loops works fine. Anything over 5 causes log in failures, this is what lead me to check the session to see where it was handled. Thanks. Mord sebb-2-2 wrote: > > On 22/02/2009, Mordechai <[email protected]> wrote: >> >> Hi, >> >> After recording several scripts in Jmeter against an in house >> application >> that seems to set a cookie which contains the jsession id I'm unable to >> find >> it in Jmeter script. After checking the headers, and the actual jmx >> file I >> cannot find where Jmeter is passing or receiving the cookie. When I use >> other proxy recorders such as fiddler, or httpwatch I can see where the >> cookie is set and where its sent. > > JMeter does not record cookies. > > When recording, the browser manages cookies. > When replaying, you need to add a Cookie Manager to manage the cookies. > > You can see cookies in the Tree View Listener. > >> Though when I check these exact requests in Jmeter the values are not >> captured or sent in the header. I'm using the cookie manager, I've >> tried >> re-recording the script a few times, and I'm still not seeing the >> jessionid >> captured. The script will work with up to 5 users and then will start >> screwing up due to session issues. > > How does the application determine the session id? > Do you need to log in? > If so, are the logins unique? > > Note that the default Http Sampler may share connections between > threads. The HttpClient Http Sampler will never do so. > >> If anyone has any idea or suggestions please let me know. >> Thanks. >> Mord >> >> P.S. I can see in httpwatch that its sent in a header as cookie but in >> Jmeter it records it without the cookie being sent in the header or set >> at >> all - am I missing something? How can I enter a cookie into the cookie >> manager if I have no where to regex the jessionid from? >> >> -- >> View this message in context: >> http://www.nabble.com/Jmeter-proxy-recoring-not-showing-cookie-tp22150874p22150874.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] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > -- View this message in context: http://www.nabble.com/Jmeter-proxy-recoring-not-showing-cookie-tp22150874p22156918.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]
