Sebb, unfortunately upgrading JMeter up to 2.3.2 didn't resolve the problem. I got exactly same results.
Could you please send me JMeter tests example that you did? Also, if you have some time, maybe you will have a look at our sample which reproduces the problem. The test logs in to nabble.com forum and then goes to user's account settings page. If you run the test, please set your account data in setup.jmx http://www.nabble.com/file/p20479566/jmeter_test_example.zip jmeter_test_example.zip Thanks, Ivan. sebb-2-2 wrote: > > On 13/11/2008, IvanIC <[EMAIL PROTECTED]> wrote: >> >> Hi sebb, >> >> >> >I'm not sure I understand what the OP is trying to do, >> >> you may see the details in my reply to Adrian ("RE: Need an advice on how >> to >> share https session between test plans - IvanIC Nov 13, 2008; 01:22pm") >> . I >> have also attached sample test plans which reproduce the problem in >> JMeter >> 2.3.1. >> >> I have couple questions about the test you did. >> >> >In my test, the first sampler does not send any cookies, but the >> >second sends the cookie that was returned in the first response. >> >> >> Does your first sampler contain several HTTP requests? > > No, just one HTTP request. > >> As in our case a >> script which is included (setup.jmx) contains several HTTP requests and >> indeed in the 1st HTTP request it does not send any cookie like in your >> example, but consequent requests in setup.jmx plan use cookies returned >> on >> the 1st request. BUT the problem is that main.jmx test plan cannot >> access >> those cookies obtained in setup.jmx. >> >> If I get your example correctly, then the main test plan (second sampler >> in >> your terms), can access cookies obtained in included test plan (first >> sampler in your terms). And that's exactly what does not work for me. > > Yes, it does work for me. I tested on 2.3.2 as I assumed you were > using the current version. > >> I used JMeter 2.3.1 and now I am going to try JMeter 2.3.2. Maybe this >> will >> resolve the problem. > > Hopefully. > >> Best regards, >> Ivan. >> >> >> >> sebb-2-2 wrote: >> > >> > On 11/11/2008, Fitzpatrick, Adrian <[EMAIL PROTECTED]> wrote: >> >> >> >> Hi Ivan, >> >> >> >> Ok, I understand a bit better now I think. Am I right in thinking >> that >> >> if you >> >> have the set-up, main test and tear-down all in a single script then >> it >> >> works >> >> fine, with multiple threads running? But if you extract the set-up >> and >> >> tear-down into separate, included scripts then you have this >> problem? >> >> >> >> If that's correct, then could this to be to do with the HTTP cookie >> >> manager >> >> JMETER element? I would guess that in this set-up you would want a >> >> cookie >> >> manager in the main script only, and not in the included set-up and >> >> tear-down >> >> scripts? I'm thinking that if you have separate cookie managers in >> your >> >> included scripts, this could cause the sessions for the included >> >> portions to >> >> be tracked independently of the main script. >> >> >> >> Otherwise you could be dealing with a potential JMETER bug re. >> tracking >> >> of >> >> cookies when using included scripts..... >> > >> > I'm not sure I understand what the OP is trying to do, but I have just >> > done a test with an include script and the Cookie Manager does work >> > for me. This is what I tried: >> > >> > Thread Group >> > + Http Defaults (set this to a site that sends cookies, e.g. google) >> > + Cookie Manager >> > + Include file containing single sampler >> > + Http Sampler >> > + Tree View >> > >> > In my test, the first sampler does not send any cookies, but the >> > second sends the cookie that was returned in the first response. >> > >> > Note that using multiple Cookie Managers will cause a problem >> > (regardless of whether includes are used) because the cookies are >> > stored by the manager. Managers don't share cookies with other >> > managers. >> > >> > This was using 2.3.2. >> > >> >> >> >> - Adrian >> >> >> >> >> >> ************************ >> >> >> >> This message has been delivered to the Internet by the Revenue >> Internet >> >> e-mail service (OP) >> >> >> >> ************************* >> >> >> >> >> --------------------------------------------------------------------- >> >> 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/Need-an-advice-on-how-to-share-https-session-between-test-plans-tp20443509p20479152.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/Need-an-advice-on-how-to-share-https-session-between-test-plans-tp20443509p20479566.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]
