idError » JAVA-JDBC

No Suitable Driver exception

admin — Fri, 20 Mar 2009 10:28:59 +0000

Applies to:
NA

Description:
Occurs while connecting to a database using JDBC.

Cause:
This exception has two potential causes. You driver is being loaded incorrectly or
Your connection URL is incorrect and the driver You want to use isn’t recognizing it.

NoClassDefFoundError exception when loading driver

admin — Fri, 20 Mar 2009 10:28:59 +0000

Applies to:
NA

Description:
Occurs while connecting to a database using JDBC.

Cause:
Your classpath is incorrect and Java cannot find the driver you want to use.

NoClassDefFoundError: org/aspectj/lang/Signature

admin — Fri, 20 Mar 2009 10:28:59 +0000

Applies to:
NA

Description:
Occurs while connecting to a database using JDBC.

Cause:
This issue relates to some confusion on the MySQL site between the normal MySQL driver and a special debugging/tracing mode driver. This error indicates that you are attempting to use the tracing driver instead of the normal driver.

Connection refused exception

admin — Fri, 20 Mar 2009 10:28:59 +0000

Applies to:
NA

Description:
Occurs while connecting to a database using JDBC.

Cause:
There are several things you need to check to isolate the source of this type of exception.
1. Your database server is accepting TCP connections.
2. Check that your database server is running on the server address you think it is
3. Check for firewalls. Is there a port or ports being blocked between your application and the database?
4. Check that you are not having a security problem. Is your application an Applet? If you are connecting to a database that is not on the same physical box as your web server then you need to sign your applet.
5. Check that you are using the right username and password
6. Check that the database user has the correct permissions and is able to log in from the location you are attempting to log in from.
7. Check that you are using the correct driver for your database. There often different versions of the same driver for the same database but different versions of the database since the underlying protocol had some changes between versions.

Strange exception when applet tries to make a connection to the DB

admin — Fri, 20 Mar 2009 10:28:59 +0000

Applies to:
NA

Description:
Occurs while connecting to a database using JDBC.

Cause:
You have tried to make a connection to the DB in applet.

Out of Memory Error when using huge datasets

admin — Fri, 20 Mar 2009 10:28:59 +0000

Applies to:
NA

Description:
Occurs while using huge result sets.

Cause:
You have tried to use huge result set, for instance, more than with 100,000 rows.

Fetch out of sequence error

admin — Fri, 20 Mar 2009 10:28:59 +0000

Applies to:
NA

Description:
Occurs when fetching values for columns more than once.

Cause:
This type of error happens because your JDBC driver only supports fetching values for columns once AND in the order that they appear in your ResultSet. For example:
while (rs.next()){
rs.getString(1);
rs.getString(3);
rs.getString(3);// error happens here
rs.getString(2);// error would also happen here
}

Data source name not found and no default driver specified Vendor: 0

admin — Fri, 20 Mar 2009 10:28:59 +0000

Applies to:
NA

Description:
This type of error occurs during an attempt to connect to a database with the bridge.

Cause:
You have tried to connect to a database with the bridge

Can’t invoke the ResultSet methods afterLast and beforeFirst

admin — Fri, 20 Mar 2009 10:28:59 +0000

Applies to:
NA

Description:
Occurs while using invalid JDBC driver.

Cause:
You are probably using a driver implemented for the JDBC 1.0 API.