Eclipse Community Forums: Test and Performance Tools Platform (TPTP)

Home » Archived » Test and Performance Tools Platform (TPTP) » jdbc

Tue, 26 July 2005 01:36

Eclipse User

Originally posted by: andy.roesch.a-city.de

Hi folks,
has anybody experience with profiling applications using odbc:jdbc. I wrote
an application which runs smoothly, but if trying to profile it, the
following error occurs:
ava.sql.SQLException: [Microsoft][ODBC Driver Manager] Der Datenquellenname
wurde nicht gefunden, und es wurde kein Standardtreiber angegeben

at sun.jdbc.odbc.JdbcOdbc.createSQLException(JdbcOdbc.java:6958 )

at sun.jdbc.odbc.JdbcOdbc.standardError(JdbcOdbc.java:7115)

at sun.jdbc.odbc.JdbcOdbc.SQLDriverConnect(JdbcOdbc.java:3074)

at sun.jdbc.odbc.JdbcOdbcConnection.initialize(JdbcOdbcConnecti on.java:323)

at sun.jdbc.odbc.JdbcOdbcDriver.connect(JdbcOdbcDriver.java:174 )

at java.sql.DriverManager.getConnection(DriverManager.java:512)

at java.sql.DriverManager.getConnection(DriverManager.java:171)

at roe.util.DataBase.OpenDB(DataBase.java:66)

at roe.control.DBObjects.OpenDB(DBObjects.java:505)

at roe.visual.MyApp.<init>(MyApp.java:434)

at roe.visual.MyApp.main(MyApp.java:873)

Has anybody any idea what might crash the app. I experienced this behaviour
with hyades 2 as well.

Re: jdbc [message #23857 is a reply to message #23615]

Thu, 28 July 2005 10:45

Eclipse User

Here's a wild guess (after using a German to English translator :):
It seems that your JDBC application fails because it can't locate your
database. If you're specifying the path to your DB relatively, then try
changing it to an absolute path before profiling it. The profiler may be
changing the current working directory that you may be expecting in your
application. Hard code the absolute path and see if this resolves the
problem. If so, then you can find better means of specifying your DB path.

Hope this helps,

Ali M.

"Andreas R

Re: jdbc [message #23938 is a reply to message #23615]

Thu, 28 July 2005 11:13

Eclipse User

A second possibility could be that the profiler is modifying your classpath,
making your application unable to locate the JDBC drivers. Make sure the
JDBC driver jar files are in your classpath (which you can specify in the
launch configuration of the profiler).

"Andreas R

Previous Topic:	get an agent to run on WAS 5.1
Next Topic:	Timed Plugin-tests

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Jul 13 13:55:10 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter