Return-Path: Delivered-To: apmail-jakarta-jmeter-user-archive@www.apache.org Received: (qmail 58329 invoked from network); 22 Nov 2008 16:06:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Nov 2008 16:06:23 -0000 Received: (qmail 35370 invoked by uid 500); 22 Nov 2008 16:06:26 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 35353 invoked by uid 500); 22 Nov 2008 16:06: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 35341 invoked by uid 99); 22 Nov 2008 16:06:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Nov 2008 08:06:25 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of sebbaz@gmail.com designates 72.14.220.159 as permitted sender) Received: from [72.14.220.159] (HELO fg-out-1718.google.com) (72.14.220.159) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Nov 2008 16:05:02 +0000 Received: by fg-out-1718.google.com with SMTP id 22so1076981fge.1 for ; Sat, 22 Nov 2008 08:05:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=oXewrLtoYVhOrRg2MfjeTXAdi1UwGxbolyexYXaMleI=; b=BdklbQIuAiV1unTKKcC1UM5CleJ0w5+KoR1zBzpiqJnslIxESTqdn2/GcuMoyHE8C5 JVUCzE1FL2jpFTbi6mof0APIiH7M6tSomBXwGGDQxgshs8UhWPtxNhD81dCdvioiPdC3 M4GlhfLDochFdxrdAiZ0kn85pe1Qc9tnyNBKQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=f/vsRE++q5H2LTh99kBWJnbZJ0ZCSWEnLw1WXy+ah6Ese1SEKN/yo2yPFl4E2AsBJF UT2x/6sPOvUptp3fnleQ8TJ5K7fqKcg+DkJuU/E4McQjibQHueepdcSdbZTsLfvEsDZU m/zZNMq2G4IC3yynCMkRXE8LTXsEgIKS7SmJo= Received: by 10.86.4.14 with SMTP id 14mr1219021fgd.76.1227369937620; Sat, 22 Nov 2008 08:05:37 -0800 (PST) Received: by 10.86.65.7 with HTTP; Sat, 22 Nov 2008 08:05:37 -0800 (PST) Message-ID: <25aac9fc0811220805m675cdcb2g9ee5e00aafbc0d36@mail.gmail.com> Date: Sat, 22 Nov 2008 16:05:37 +0000 From: sebb To: "JMeter Users List" Subject: Re: jmeter.protocol.jdbc.config.DataSourceElement: Could not return Connection java.sql.SQLException: No suitable driver In-Reply-To: <25aac9fc0811191150m7a70dfe0i27ac1c65f2d90cbf@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <953908420811191019q22710e21m7cd5ead4f1b8f9b7@mail.gmail.com> <25aac9fc0811191049i69a65b58i37669a5d538d7340@mail.gmail.com> <953908420811191137h56db1cebnf3e2293817d85191@mail.gmail.com> <25aac9fc0811191149w350a30d0id843be48d21d84cd@mail.gmail.com> <25aac9fc0811191150m7a70dfe0i27ac1c65f2d90cbf@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org On 19/11/2008, sebb wrote: > On 19/11/2008, Parvathaneni, Sireesha wrote: > > > > > > On Wed, Nov 19, 2008 at 1:49 PM, sebb wrote: > > > > > > > > > > > > > > > > On 19/11/2008, Parvathaneni, Sireesha > > wrote: > > > > Hi > > > > > > > > I was trying to run Jmeter DB tests remotely for postgreSQl db and i had > > put > > > > the jdbc-pgsql driver .jar file under /jmeterserver/lib but still seeing > > > > below messages > > > > > > > > driver iusing to connect to PostGreSQL DB : postgresql-8.3-603.jdbc4.jar > > > > > > > > starting remotely : Start -> Remote Start -> Remote Server > > > > > > > > WARN - jmeter.protocol.jdbc.config.DataSourceElement: > > > > Could not return Connection java.sql.SQLException: No suitable driver > > > > at > > > > > > java.sql.DriverManager.getConnection(DriverManager.java:545) > > > > at > > > > > > java.sql.DriverManager.getConnection(DriverManager.java:171) > > > > at > > > > > > org.apache.avalon.excalibur.datasource.JdbcConnectionFactory.newInstance(JdbcConnectionFactory.java:185) > > > > at > > > > > > org.apache.avalon.excalibur.pool.ResourceLimitingPool.newPoolable(ResourceLimitingPool.java:672) > > > > at > > > > > > org.apache.avalon.excalibur.pool.ValidatedResourceLimitingPool.newPoolable(ValidatedResourceLimitingPool.java:178) > > > > at > > > > > > org.apache.avalon.excalibur.datasource.ResourceLimitingJdbcConnectionPool.newPoolable(ResourceLimitingJdbcConnectionPool.java:123) > > > > at > > > > > > org.apache.avalon.excalibur.pool.ResourceLimitingPool.get(ResourceLimitingPool.java:402) > > > > at > > > > > > org.apache.avalon.excalibur.pool.ValidatedResourceLimitingPool.get(ValidatedResourceLimitingPool.java:130) > > > > at > > > > > > org.apache.avalon.excalibur.datasource.ResourceLimitingJdbcDataSource.getConnection(ResourceLimitingJdbcDataSource.java:222) > > > > at > > > > > > org.apache.jmeter.protocol.jdbc.config.DataSourceElement$DataSourceComponentImpl.getConnection(DataSourceElement.java:267) > > > > at > > > > > > org.apache.jmeter.protocol.jdbc.config.DataSourceElement.getConnection(DataSourceElement.java:137) > > > > at > > > > > > org.apache.jmeter.protocol.jdbc.sampler.JDBCSampler.sample(JDBCSampler.java:155) > > > > at > > > > > > org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:290) > > > > at java.lang.Thread.run(Thread.java:595) > > > > > > > > Help me, let me know if need to do anything more.Thanks in advance! > > > > > > Does it work if you use JMeter in GUI mode (i.e. not Client-Server)? > > > Try running that on the server node if you can. > > > > > > Yes, its working on client machine but not running through server. Getting > > above messages while running on server. > > > Are there any other errors logged by the DataSourceElement? > > JDBC works fine for me in client-server mode, but when the classname > is missing I get an extra error message. > It turns out that the JDBC jar had been added correctly to the lib directory, but the server had not been restarted, so it did not update its classpath. > > > > > > > > > Are you sure that the jdbc jar is in the correct directory on the server? > > > The correct directory will contain several other jars, e.g. > > > commons-logging, jorphan etc. > > > > > > it is under /lib/ on jmeterserver , hope this is the right place as > > found the above mentioned jars(commons-logging, jorphan etc) in the same > > place. > > > > > > > > > Are you sure the correct classname is used, and is present in the jar? > > > > > > The clasname in JDBC config is :org.postgresql.Driver which is located in > > jar file : under org.postgresql.Driver.class > > > > > > > > > > Rgrds, > > > > Siri > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > 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