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]
