You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by de...@geronimo.apache.org on 2004/09/17 02:45:37 UTC
[jira] Created: (GERONIMO-306) Implement jdbc driver specific ExceptionSorter classes
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/GERONIMO-306
Here is an overview of the issue:
---------------------------------------------------------------------
Key: GERONIMO-306
Summary: Implement jdbc driver specific ExceptionSorter classes
Type: Task
Status: Unassigned
Priority: Major
Project: Apache Geronimo
Components:
connector
Versions:
1.0-M3
Assignee:
Reporter: David Jencks
Created: Thu, 16 Sep 2004 5:45 PM
Updated: Thu, 16 Sep 2004 5:45 PM
Description:
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.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-306) Implement jdbc driver specific
ExceptionSorter classes
Posted by "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.
[jira] Updated: (GERONIMO-306) Implement jdbc driver specific ExceptionSorter classes
Posted by "Matt Hogstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-306?page=all ]
Matt Hogstrom updated GERONIMO-306:
-----------------------------------
Fix Version: 1.x
(was: 1.0)
Moved to 1.x
> Implement jdbc driver specific ExceptionSorter classes
> ------------------------------------------------------
>
> Key: GERONIMO-306
> URL: http://issues.apache.org/jira/browse/GERONIMO-306
> Project: Geronimo
> Type: Task
> Components: connector
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-306) Implement jdbc driver specific ExceptionSorter classes
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-306?page=all ]
Aaron Mulder updated GERONIMO-306:
----------------------------------
Fix Version: 1.0
Description:
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.
was:
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.
Environment:
Here's a starter list of JDBC-compliant products:
DaffodilDB
DB2
Derby
FrontBase
HSQLDB
Informix
JDataStore
JDBC/ODBC Bridge
McKoi
Mimer
MySQL
Oracle
Pervasive
Pointbase
PostgreSQL
Progress
MaxDB
SQL Server
Sybase
> Implement jdbc driver specific ExceptionSorter classes
> ------------------------------------------------------
>
> Key: GERONIMO-306
> URL: http://issues.apache.org/jira/browse/GERONIMO-306
> Project: Geronimo
> Type: Task
> Components: connector
> Versions: 1.0-M3
> Reporter: David Jencks
> Fix For: 1.0
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira