Return-Path: Delivered-To: apmail-jakarta-jmeter-user-archive@www.apache.org Received: (qmail 50561 invoked from network); 12 Mar 2009 13:20:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Mar 2009 13:20:42 -0000 Received: (qmail 7520 invoked by uid 500); 12 Mar 2009 13:20:36 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 7497 invoked by uid 500); 12 Mar 2009 13:20:36 -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 7486 invoked by uid 99); 12 Mar 2009 13:20:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Mar 2009 06:20:36 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of sebbaz@gmail.com designates 209.85.219.177 as permitted sender) Received: from [209.85.219.177] (HELO mail-ew0-f177.google.com) (209.85.219.177) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Mar 2009 13:20:28 +0000 Received: by ewy25 with SMTP id 25so353284ewy.37 for ; Thu, 12 Mar 2009 06:20:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=ohSA2+VJco7VsgHWnPhAfJ1dMjdwCm59VtS2UIeor2U=; b=jOEuEpwjeUXLLeHoLn3u+f2CSZNuNAP0tCDmoYq0zBnnjD5AlZL+5TL7liXfFBolqm J55D7qqn2Cv2pC0guUHc7304UGAZnWm2nMA35ZRZXMfwnL4iy2ePCMAyRU3lb5dcsh/I +ukmNW1Zk3LAiGQAmfskOWMxWqE7PZpXV0yUU= 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:content-transfer-encoding; b=nYNwovJkVH1jxsVKFuwIsrvTzo2NnvO8p+tCqLgdeOaVXXo0leJg693SUxvlfbmE+l hKC+ArZHLAb794XEUds6guwcim5F+1Uf+6ABgKQ+4vHGqsj2ROsBEBy3T9Ti4Zaxvd7y LTUn//dN0FHbdre/qZ4y8z/hmZ6YOLm/rR8N4= MIME-Version: 1.0 Received: by 10.210.45.17 with SMTP id s17mr6461033ebs.93.1236864008263; Thu, 12 Mar 2009 06:20:08 -0700 (PDT) In-Reply-To: <7ac2300c0903120525j7c8477fcw89475dca0e1abc41@mail.gmail.com> References: <7ac2300c0903120525j7c8477fcw89475dca0e1abc41@mail.gmail.com> Date: Thu, 12 Mar 2009 13:20:08 +0000 Message-ID: <25aac9fc0903120620v63b79811rd2388520e3d6f17@mail.gmail.com> Subject: Re: JDBC Request and Connection Pools From: sebb To: JMeter Users List Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 12/03/2009, aidy lewis wrote: > Hi, > > Regarding the JDBC Request, if I have 100 threads to simulate 100 > users wouldn't I want connection pooling to be turned off. I think you would *always* want it turned off if you are trying to test a server via JDBC... I'm not sure what the use case for using pooling is, given that JMeter threads are intended to represent independent users. > In the JDBC Connection Configuration would that mean I set the maximum > number of pool connections to 1? Which is why there is an option to have 1 connection per-thread by setting the pool count to 0 (zero). > Aidy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: jmeter-user-help@jakarta.apache.org