Return-Path: X-Original-To: apmail-jmeter-user-archive@www.apache.org Delivered-To: apmail-jmeter-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C8BA8D87A for ; Fri, 2 Nov 2012 01:21:51 +0000 (UTC) Received: (qmail 43345 invoked by uid 500); 2 Nov 2012 01:21:51 -0000 Delivered-To: apmail-jmeter-user-archive@jmeter.apache.org Received: (qmail 43318 invoked by uid 500); 2 Nov 2012 01:21:51 -0000 Mailing-List: contact user-help@jmeter.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "JMeter Users List" Delivered-To: mailing list user@jmeter.apache.org Received: (qmail 43302 invoked by uid 99); 2 Nov 2012 01:21:51 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Nov 2012 01:21:51 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [113.197.125.11] (HELO relaybrisbn.tnsi.com) (113.197.125.11) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Nov 2012 01:21:44 +0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap0EAP8ek1CsEU3h/2dsb2JhbABExDqCHgEBBAE6RAsCAQgNKRAyJQEBBBuHeL0skVVhA5wEjTg X-IronPort-AV: E=Sophos;i="4.80,696,1344207600"; d="scan'208";a="881601" Received: from unknown (HELO mail-hub-ap.win2k.corp.tnsi.com) ([172.17.77.225]) by relaybrisbn.tnsi.com with ESMTP/TLS/RC4-MD5; 02 Nov 2012 01:22:39 +0000 Received: from TNS-MAIL-AP.win2k.corp.tnsi.com ([172.17.77.231]) by mail-hub-ap.win2k.corp.tnsi.com ([172.17.77.225]) with mapi; Fri, 2 Nov 2012 11:21:22 +1000 From: "Stott, Charlie" To: JMeter Users List Date: Fri, 2 Nov 2012 11:21:21 +1000 Subject: RE: setup & teardown thread group concurrency Thread-Topic: setup & teardown thread group concurrency Thread-Index: Ac24JJ+//wOj38P7SPe1+2BZgKT0QAAYf8Hg Message-ID: <2DB71565D9DF26409875BE0660934F6B5F58085E0C@TNS-MAIL-AP.win2k.corp.tnsi.com> References: <2DB71565D9DF26409875BE0660934F6B5F57F7961E@TNS-MAIL-AP.win2k.corp.tnsi.com> In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Hi, Thanks for the reply. > > I am finding that the setup thread appears to run concurrently with all= the other thread groups. > What makes you think that? I have a pre-processor which stores a value in a property in the setup thre= ad group. Samples that are processed in setup thread group respect the value of the p= roperty, but samples processed in other thread groups have not got it set y= et, although it often becomes set during the processing of the group. I understand scope of properties is global. I also notice that some setup = samples process after samples from non-setup thread group. I find the behaviour is different depending if I set the consecutive settin= g in the test plan. Are properties asynchronous? That might also explain the behaviour? I th= ink I need to understand scope and function much better with regard to prop= erties and variables. I understand that variables are local to thread group, but is this also tru= e in the case of setup thread (I assumed it was due to concurrency). On co= mpletion of the setup thread group, will all variables changes be discarded= ? I think I might have assumed that other thread groups threads were actua= lly started after completion of setup threads, but perhaps they are all sta= rted early, then delayed until setup is complete? I will try to provide a simple test plan snippet to check my expectations w= ith the group. > > Is this proper behaviour? > No. Thanks particularly for confirming this. It means I don't mind persevering= to work out what I am doing wrong. Cheers, Charlie --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org For additional commands, e-mail: user-help@jmeter.apache.org