On 13/11/2008, IvanIC <[EMAIL PROTECTED]> wrote: > > Hi Adrian, > > yes, this is what exactly what we have: > > >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? > > > Regarding this note below. We have removed Cookie > http://www.nabble.com/file/p20478940/jmeter_test_example.zip > jmeter_test_example.zip Manager element from setup.jmx and teardown.jmx > test plans and in the main test plan we tried two cases: > a) put Cookie Manager element in "Thread Group". > b) put Cookie Manager element in the root node of test plan. > For the case a) we had next effect: in setup.jmx test plan for every HTTP > request a new session was created. > For the case b) we had another effect: in setup.jmx plan a single session > was created for all HTTP requests within a single thread in setup.jmx. But > this session was a different one from the session in main test plan. > > Andrian, please let me know if you have more thoughts on this. > > Attached is a simplified example which demonstrates 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 > > JMeter version: 2.3.1
There was a problem with the Cookie Manager in 2.3.1: http://wiki.apache.org/jakarta-jmeter/CookieManagerBugIn231 2.3.2 has lots of other fixes; I suggest you upgrade. > Best regards, > Ivan. > > > >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. > > > > Fitzpatrick, Adrian 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..... > > > > - 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] > > > > > > > > http://www.nabble.com/file/p20478940/jmeter_test_example.zip > jmeter_test_example.zip > > -- > View this message in context: > http://www.nabble.com/Need-an-advice-on-how-to-share-https-session-between-test-plans-tp20443509p20478940.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]
