[jira] Commented: (GERONIMO-306) Implement jdbc driver specific ExceptionSorter classes

["David Jencks (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GERONIMO-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756860#action_12756860 ] 

David Jencks commented on GERONIMO-306:
---------------------------------------

no one really stepped up for this until GERONIMO-4222.  As noted there, msany dbs provide PooledDataSource implementations that allegedly recognize fatal connection errors.  We shoudl wrpa those when available.

In the generic tranql wrapper I implemented a sorter that allows a list of SQLCodes that are allegedly known to be non-fatal.

> Implement jdbc driver specific ExceptionSorter classes
> ------------------------------------------------------
>
>                 Key: GERONIMO-306
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-306
>             Project: Geronimo
>          Issue Type: Task
>          Components: connector
>    Affects Versions: 1.0-M3
>            Reporter: David Jencks
>             Fix For: 1.x
>
>
> I've added a framework for driver specific exception handling in tranql connector.
> Each jdbc driver needs an ExceptionSorter subclass that can tell if the various SQLExceptions thrown by the driver mean that the connection is no longer usable.
> To use this with a particular driver, pack the ExceptionSorter subclass into a jar (along with any other driver specific stuff) and use a dependency element in geronimo-ra.xml to include this jar (and another for the driver itself) in the classpath.
> This is a great opportunity to contribute to geronimo without learning much about geronimo internals.

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