commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Steitz (JIRA)" <>
Subject [jira] Updated: (DBCP-143) [dbcp] SQLNestedException thrown by server causes client ClassNotFoundException.
Date Mon, 10 Jul 2006 05:27:34 GMT
     [ ]

Phil Steitz updated DBCP-143:

    Bugzilla Id:   (was: 37181)
    Fix Version: 1.3

> [dbcp] SQLNestedException thrown by server causes client ClassNotFoundException.
> --------------------------------------------------------------------------------
>          Key: DBCP-143
>          URL:
>      Project: Commons Dbcp
>         Type: Bug

>  Environment: Operating System: other
> Platform: Other
>     Reporter: Andreas Krüger
>      Fix For: 1.3

> 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 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?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message