Hi,

I actually started with the oracle9i-classes12.jar file and then tried with
the ojdbc14_10.1.0.4.0.jar file.  I copied the names of the files, so no
room for typos.  The only thing of interest in the log file is the error
stack trace:

2009/01/09 09:41:08 WARN  - jmeter.protocol.jdbc.config.DataSourceElement:
Could not return Connection java.sql.SQLException: No suitable driver
        at java.sql.DriverManager.getConnection(Unknown Source)
        at java.sql.DriverManager.getConnection(Unknown Source)
        at
org.apache.avalon.excalibur.datasource.JdbcConnectionFactory.newInstance(Jdb
cConnectionFactory.java:185)
        at
org.apache.avalon.excalibur.pool.ResourceLimitingPool.newPoolable(ResourceLi
mitingPool.java:672)
        at
org.apache.avalon.excalibur.pool.ValidatedResourceLimitingPool.newPoolable(V
alidatedResourceLimitingPool.java:178)
        at
org.apache.avalon.excalibur.datasource.ResourceLimitingJdbcConnectionPool.ne
wPoolable(ResourceLimitingJdbcConnectionPool.java:123)
        at
org.apache.avalon.excalibur.pool.ResourceLimitingPool.get(ResourceLimitingPo
ol.java:402)
        at
org.apache.avalon.excalibur.pool.ValidatedResourceLimitingPool.get(Validated
ResourceLimitingPool.java:130)
        at
org.apache.avalon.excalibur.datasource.ResourceLimitingJdbcDataSource.getCon
nection(ResourceLimitingJdbcDataSource.java:222)
        at
org.apache.jmeter.protocol.jdbc.config.DataSourceElement$DataSourceComponent
Impl.getConnection(DataSourceElement.java:267)
        at
org.apache.jmeter.protocol.jdbc.config.DataSourceElement.getConnection(DataS
ourceElement.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(Unknown Source)

Shelli

-----Original Message-----
From: sebb [mailto:seb...@gmail.com] 
Sent: January 8, 2009 5:39 PM
To: JMeter Users List
Subject: Re: java.sql.SQLException: No suitable driver

On 09/01/2009, Shelli D. Orton <shelli.or...@wmode.com> wrote:
> Hi,
>
>  I'm using JMeter 2.3.2 and am trying to connect to an Oracle database.  I
have included the ojdbc14_10.1.0.4.0.jar file in my JMeter's lib directory.
I've set up my JDBC Connection Configuration element's JDBC Driver class to
be "oracle.jdbc.driver.OracleDriver" (which I also confirmed exists in the
jar file).  I've closed/re-opened JMeter since adding the jar file to the
lib directory, but I still get this error:

Sounds OK, but there must be an error somewhere...

>  Thread Name: Ringback Account Manager 1-1
>  Sample Start: 2009-01-08 16:32:21 MST
>  Load time: 1
>  Latency: 1
>  Size in bytes: 0
>  Sample Count: 1
>  Error Count: 1
>  Response code: 08001 0
>  Response message: java.sql.SQLException: No suitable driver
>
>  Response headers:
>
>  Is there any other config change that I need to make?  I've used JMeter
2.1.1 in the past (with oracle9i-classes12.jar) and it worked fine
>

As far as I know, there has been little or no change in how JMeter
finds the JDBC jar.

I suggest you try a few experiments, e.g. try oracle9i-classes12.jar
with JMeter 2.3.2.

Or you can download derbyclient.jar from Apache:
http://db.apache.org/derby/derby_downloads.html to see if you can load
that (no need to start Derby itself)

Are you positive everything is spelt correctly?
Are there any other errors in the JMeter log file?

>  Thanks in advance!
>
>  Shelli
>
>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org
>  For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org
For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org
For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org

Reply via email to