[
http://jira.codehaus.org/browse/TQL-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks closed TQL-15.
---------------------------
Assignee: David Jencks
Resolution: Fixed
We think we've fixed this by
1. converting most of the local wrappers to use ConnectionPoolDataSource which has a connection event listener mechanism that is supposed to tell the pool when a connection is dead.
2. implementing an exception sorter that knows about some SQLCodes that are supposed to indicate a connection is dead. We'ere also looking for a jdbc/sql expert to review this list of codes.
If you still have problems please be more specific about which wrapper you are using, which database, and what sql exception sqlcode and errorcode you are getting.
> tranql-local adapters does not call connectionErrorOccurred
> -----------------------------------------------------------
>
> Key: TQL-15
> URL:
http://jira.codehaus.org/browse/TQL-15> Project: TranQL
> Issue Type: Bug
> Environment: Geronimo 2.1.4
> Reporter: Radim Kolar
> Assignee: David Jencks
>
>
https://issues.apache.org/jira/browse/GERONIMO-4222> It seems that tranql-local adapers do not calls connectionErrorOccurred if connection to database is lost for example because database was restarted.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
