commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Thomas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DBCP-143) [dbcp] SQLNestedException thrown by server causes client ClassNotFoundException.
Date Sun, 15 Mar 2009 22:22:50 GMT

     [ https://issues.apache.org/jira/browse/DBCP-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mark Thomas updated DBCP-143:
-----------------------------

    Fix Version/s:     (was: 1.4)
                   2.0

Removing the SQLNestedException would be an API breaking change so it would have to wait until
a DBCP 2.0 release. To be perfectly honest, I don't see a 2.0 release on the horizon right
now. However, I am not closing this as WONTFIX as it is always possible that there will be
a 2.0 release at some point but please be aware that this is some time (possibly years) away.

> [dbcp] SQLNestedException thrown by server causes client ClassNotFoundException.
> --------------------------------------------------------------------------------
>
>                 Key: DBCP-143
>                 URL: https://issues.apache.org/jira/browse/DBCP-143
>             Project: Commons Dbcp
>          Issue Type: Bug
>         Environment: Operating System: other
> Platform: Other
>            Reporter: Andreas Krüger
>             Fix For: 2.0
>
>         Attachments: DBCP-143.patch
>
>
> 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?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message