JMeter › JMeter - User

java.sql.SQLException: No suitable driver

Classic

List

Threaded

9 messages Options

Shelli D. Orton

java.sql.SQLException: No suitable driver

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:

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.

Thanks in advance!

Shelli

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

sebb-2-2

Re: java.sql.SQLException: No suitable driver

On 09/01/2009, Shelli D. Orton <[hidden email]> 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: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Shelli D. Orton

RE: java.sql.SQLException: No suitable driver

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:[hidden email]]
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 <[hidden email]> 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...

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?

Shelli D. Orton

RE: java.sql.SQLException: No suitable driver

Hi again,

I downloaded the Derby client and think I set up the test to use it
properly. I changed the JDBC Driver class to be
"org.apache.derby.jdbc.ClientDriver" and ensured that the derbyclient.jar is
in the JMeter lib directory. I left the other JDBC Connection Configuration
element settings the same figuring I'd get a different error if it found the
class and attempted to hit the database. However, I got the same
error/stack trace in the log. I did do a JMeter shutdown/restart after
copying the jar file into the lib.

This is very frustrating...

Shelli

-----Original Message-----
From: Shelli D. Orton [mailto:[hidden email]]
Sent: January 9, 2009 9:44 AM
To: 'JMeter Users List'
Subject: RE: java.sql.SQLException: No suitable driver

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:[hidden email]]
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 <[hidden email]> 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...

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Shelli D. Orton

RE: java.sql.SQLException: No suitable driver

Me again...

I still have my version of JMeter 2.1.1 installed and opened an old test to
make sure it could find the JDBC driver and it worked fine with
oracle9i-classes12.jar file. I changed to the ojdbc14_10.1.0.4.0.jar file
in the 2.1.1 lib and it still was able to access the database. I would like
to see if my new test would run in 2.1.1, but I can't open it since it was
written in 2.3.2. Can anyone tell me what if any modifications I can
manually make to the test file so it will open in 2.1.1?

Thanks
Shelli

-----Original Message-----
From: Shelli D. Orton [mailto:[hidden email]]
Sent: January 9, 2009 10:13 AM
To: 'JMeter Users List'
Subject: RE: java.sql.SQLException: No suitable driver

Hi again,

I downloaded the Derby client and think I set up the test to use it
properly. I changed the JDBC Driver class to be
"org.apache.derby.jdbc.ClientDriver" and ensured that the derbyclient.jar is
in the JMeter lib directory. I left the other JDBC Connection Configuration
element settings the same figuring I'd get a different error if it found the
class and attempted to hit the database. However, I got the same
error/stack trace in the log. I did do a JMeter shutdown/restart after
copying the jar file into the lib.

This is very frustrating...

Shelli

-----Original Message-----
From: Shelli D. Orton [mailto:[hidden email]]
Sent: January 9, 2009 9:44 AM
To: 'JMeter Users List'
Subject: RE: java.sql.SQLException: No suitable driver

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:[hidden email]]
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 <[hidden email]> 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...

Shelli D. Orton

RE: java.sql.SQLException: No suitable driver

In reply to this post by Shelli D. Orton

Hi,

Still get the same error. Thanks for the suggestion.

Shelli

-----Original Message-----
From: Turkel, David [mailto:[hidden email]]
Sent: January 9, 2009 10:17 AM
To: [hidden email]
Subject: RE: java.sql.SQLException: No suitable driver

Try putting the JAR(s) in the lib\ext directory.

-----Original Message-----
From: Shelli D. Orton [mailto:[hidden email]]
Sent: Friday, January 09, 2009 12:13 PM
To: 'JMeter Users List'
Subject: RE: java.sql.SQLException: No suitable driver

Hi again,

I downloaded the Derby client and think I set up the test to use it
properly. I changed the JDBC Driver class to be
"org.apache.derby.jdbc.ClientDriver" and ensured that the
derbyclient.jar is
in the JMeter lib directory. I left the other JDBC Connection
Configuration
element settings the same figuring I'd get a different error if it found
the
class and attempted to hit the database. However, I got the same
error/stack trace in the log. I did do a JMeter shutdown/restart after
copying the jar file into the lib.

This is very frustrating...

Shelli

-----Original Message-----
From: Shelli D. Orton [mailto:[hidden email]]
Sent: January 9, 2009 9:44 AM
To: 'JMeter Users List'
Subject: RE: java.sql.SQLException: No suitable driver

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(Resour
ceLi
mitingPool.java:672)
at
org.apache.avalon.excalibur.pool.ValidatedResourceLimitingPool.newPoolab
le(V
alidatedResourceLimitingPool.java:178)
at
org.apache.avalon.excalibur.datasource.ResourceLimitingJdbcConnectionPoo
l.ne
wPoolable(ResourceLimitingJdbcConnectionPool.java:123)
at
org.apache.avalon.excalibur.pool.ResourceLimitingPool.get(ResourceLimiti
ngPo
ol.java:402)
at
org.apache.avalon.excalibur.pool.ValidatedResourceLimitingPool.get(Valid
ated
ResourceLimitingPool.java:130)
at
org.apache.avalon.excalibur.datasource.ResourceLimitingJdbcDataSource.ge
tCon
nection(ResourceLimitingJdbcDataSource.java:222)
at
org.apache.jmeter.protocol.jdbc.config.DataSourceElement$DataSourceCompo
nent
Impl.getConnection(DataSourceElement.java:267)
at
org.apache.jmeter.protocol.jdbc.config.DataSourceElement.getConnection(D
ataS
ourceElement.java:137)
at
org.apache.jmeter.protocol.jdbc.sampler.JDBCSampler.sample(JDBCSampler.j
ava:
155)
at
org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:290)
at java.lang.Thread.run(Unknown Source)

Shelli

-----Original Message-----
From: sebb [mailto:[hidden email]]
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 <[hidden email]> 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...

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?

sebb-2-2

Re: java.sql.SQLException: No suitable driver

In reply to this post by Shelli D. Orton

On 09/01/2009, Shelli D. Orton <[hidden email]> wrote:

> Hi again,
>
> I downloaded the Derby client and think I set up the test to use it
> properly. I changed the JDBC Driver class to be
> "org.apache.derby.jdbc.ClientDriver" and ensured that the derbyclient.jar is
> in the JMeter lib directory. I left the other JDBC Connection Configuration
> element settings the same figuring I'd get a different error if it found the
> class and attempted to hit the database. However, I got the same
> error/stack trace in the log. I did do a JMeter shutdown/restart after
> copying the jar file into the lib.
>
> This is very frustrating...
>

Then there may be a problem with the installation of JMeter 2.3.2.

Try re-installing.

> Shelli
>
>
> -----Original Message-----
> From: Shelli D. Orton [mailto:[hidden email]]
> Sent: January 9, 2009 9:44 AM
> To: 'JMeter Users List'
>
> Subject: RE: java.sql.SQLException: No suitable driver
>
> 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:[hidden email]]
> 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 <[hidden email]> 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: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

EvilPeanut

Re: java.sql.SQLException: No suitable driver

In reply to this post by Shelli D. Orton

Try download ojdbc6.jar it works for me in 2.3.2. Also what java environment are you using?

Shelli D. Orton 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:

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.

Thanks in advance!

Shelli

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

sebb-2-2

Re: java.sql.SQLException: No suitable driver

I've since found out that the message "No suitable driver" generally
means that the connection string is wrong - i.e. none of the loaded
drivers were able to handle it.

If the driver class cannot be found, then the message is different.

You can see this by deliberately using a class name that cannot be
found, e.g. "invalid.Driver".

On 16/01/2009, EvilPeanut <[hidden email]> wrote:

>
> Try download ojdbc6.jar it works for me in 2.3.2. Also what java environment
> are you using?
>
>
>
> Shelli D. Orton 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:
> >
> > 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.
> >
> > Thanks in advance!
> >
> > Shelli
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
> >
>
>
> --
> View this message in context: http://www.nabble.com/java.sql.SQLException%3A-No-suitable-driver-tp21363800p21497611.html
> Sent from the JMeter - User mailing list archive at Nabble.com.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]