[DBCP-143] [dbcp] SQLNestedException thrown by server causes client ClassNotFoundException.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0

Environment

Operating System: other
Platform: Other

• Bugzilla Id: 37181
• Assignee: Unassigned
• Reporter: Andreas Krüger
• Created: 20/Oct/05 20:18
• Updated: 24/Feb/15 03:23
• Resolved: 23/Jul/13 23:09

Description

This is a GUI client / application server / database server application.

On the GUI client side, we see java.lang.ClassNotFoundException:
org.apache.commons.dbcp.SQLNestedException.

This happens when the database server is down, DBCP cannot connect to the
database, and throws a org.apache.commons.dbcp.SQLNestedException.

Our application server code sends the java.sql.SQLException it sees to the
client via RMI.

However, on the client, we have not provided commons-dbcp.jar.

And I don't think we should - DBCP is server code.

But, when the client does not have SQLNestedException's class file, the attempt
to de-serialize it results in the ClassNotFoundException we've been seeing.

Even old http://java.sun.com/j2se/1.3/docs/api/java/sql/SQLException.html has
the facilities that SQLNestedExcepion offers: It is able to chain another
SQLException to itself. So while SQLNestedException clearly causes problems, I
don't understand what DBCP gains from it.

What would we loose if it were scratched?

Issue Links

• relates to: DBCP-310 SQLNestedException & use of initCause() with SQLException