Return-Path: X-Original-To: apmail-jakarta-jmeter-user-archive@www.apache.org Delivered-To: apmail-jakarta-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 2F9764A07 for ; Sat, 4 Jun 2011 17:34:26 +0000 (UTC) Received: (qmail 57135 invoked by uid 500); 4 Jun 2011 17:34:25 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 57114 invoked by uid 500); 4 Jun 2011 17:34:25 -0000 Mailing-List: contact jmeter-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "JMeter Users List" Reply-To: "JMeter Users List" Delivered-To: mailing list jmeter-user@jakarta.apache.org Received: (qmail 57105 invoked by uid 99); 4 Jun 2011 17:34:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Jun 2011 17:34:25 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of flyingrhenquest@gmail.com designates 209.85.213.44 as permitted sender) Received: from [209.85.213.44] (HELO mail-yw0-f44.google.com) (209.85.213.44) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Jun 2011 17:34:17 +0000 Received: by ywp31 with SMTP id 31so1468028ywp.31 for ; Sat, 04 Jun 2011 10:33:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=gWJmb7+MVriLBc3kHOSk7AcTCk0M7SUjPD/TWrAbcec=; b=VByZpLLv4bZgboLNGMVPreC60loM/rnzKGM6ob8N4ZFpK3cEXoJk4qXR2mtvlnpvJ6 NzccbZiSGW7i9FQbRveI08fsjITdLo95sDiXhDQH/QDEweba1fw8egW/zANiGhwNPRlq I+k8vvSyFoG4yhJNMPTIBhqE7UuTJ6hcDXwxQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=dtkh9AkpZF/o2ewZCJ9TAnIilUDZj0friXjSAuedwjEWNxzMdlUq7vi9kIpTS5Qr5Q knYT/DebVZDoGv3ASkED2y9iZQpKHFo4VX90SyBsiaqoXU/iQP9YTf+Dj8JSYGnTJZm9 SXLVEEVDvYGlUDq1mB5xF4WFajsaWqFLNEhD4= MIME-Version: 1.0 Received: by 10.150.131.18 with SMTP id e18mr2775523ybd.352.1307208836614; Sat, 04 Jun 2011 10:33:56 -0700 (PDT) Received: by 10.151.10.18 with HTTP; Sat, 4 Jun 2011 10:33:56 -0700 (PDT) In-Reply-To: References: <1307175999890-4453447.post@n5.nabble.com> <1307182912758-4453629.post@n5.nabble.com> <1307183434837-4453640.post@n5.nabble.com> <1307186235095-4453743.post@n5.nabble.com> <1307186731116-4453759.post@n5.nabble.com> <1307188135548-4453787.post@n5.nabble.com> Date: Sat, 4 Jun 2011 11:33:56 -0600 Message-ID: Subject: Re: Using values from DB for a HTTP request From: Bruce Ide To: JMeter Users List Content-Type: multipart/alternative; boundary=000e0cd484bc5a8b8904a4e646bc X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd484bc5a8b8904a4e646bc Content-Type: text/plain; charset=ISO-8859-1 I believe you always get an array, even if only 1 thing is returned. If you request more than 1 column from the database you can use a comma separated list of variables. If you haven't tried a simple test to see what it does, I suggest doing so. Just make a test with a JDBC Config data element, a view results tree listener, a thread group, a JDBC query that sets variables and a debug sampler. The debug sampler is your friend. The two things you want to look at in the results tree after you run your test are the JDBC request results tab and the debug sampler. Verify that your JDBC results did, in fact, retrieve columns from the database. Then look at the debug sampler and see how it created the variables for you to use. -- Bruce Ide FlyingRhenquest@gmail.com --000e0cd484bc5a8b8904a4e646bc--