Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 6887A200D4B for ; Mon, 27 Nov 2017 11:58:39 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 67013160C13; Mon, 27 Nov 2017 10:58:39 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id ADC97160C02 for ; Mon, 27 Nov 2017 11:58:38 +0100 (CET) Received: (qmail 2118 invoked by uid 500); 27 Nov 2017 10:58:37 -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 2106 invoked by uid 99); 27 Nov 2017 10:58:37 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Nov 2017 10:58:37 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id E76B518030B for ; Mon, 27 Nov 2017 10:58:36 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.28 X-Spam-Level: X-Spam-Status: No, score=0.28 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id Va6zdC8Roro6 for ; Mon, 27 Nov 2017 10:58:32 +0000 (UTC) Received: from forward106o.mail.yandex.net (forward106o.mail.yandex.net [37.140.190.187]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 7EDFE5F216 for ; Mon, 27 Nov 2017 10:58:31 +0000 (UTC) Received: from mxback7j.mail.yandex.net (mxback7j.mail.yandex.net [IPv6:2a02:6b8:0:1619::110]) by forward106o.mail.yandex.net (Yandex) with ESMTP id EBACE782BEB for ; Mon, 27 Nov 2017 13:58:24 +0300 (MSK) Received: from web39o.yandex.ru (web39o.yandex.ru [2a02:6b8:0:1a2d::5:219]) by mxback7j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id 6gFrfpeDaX-wOSC6ekq; Mon, 27 Nov 2017 13:58:24 +0300 Received: by web39o.yandex.ru with HTTP; Mon, 27 Nov 2017 13:58:24 +0300 From: Konstantin Kalinin To: user@jmeter.apache.org Subject: Does JDBC Connection Config component respect its scope? MIME-Version: 1.0 Message-Id: <159471511780304@web39o.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Mon, 27 Nov 2017 14:58:24 +0400 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=utf-8 archived-at: Mon, 27 Nov 2017 10:58:39 -0000 Hello! I'm using JMeter 3.3. I try to setup a JDBC Connection Config (JDBC CC) this way: Test plan |__setUp Thread Group |__Sampler1 (sets variables) |__JDBC Request1 |__JDBC CC (using vars from Sampler1) Seems that JDBC CC initializes when Test plan is loaded, no matter where it is in the plan, as it can not use variables that I've set in Sampler1. Adding some tree levels with different Controllers changes nothing. It behaves like a User Defined Variables config element do, but there's no note about it in a Documentation. I expect, that JDBC CC would respect it's scope. Is it a bug? --  Konstantin Kalinin +7 912 468 00 00 --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org For additional commands, e-mail: user-help@jmeter.apache.org