[
https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756858#action_12756858
]
David Jencks commented on GERONIMO-4222:
----------------------------------------
Absolutely the best solution for this kind of problem is to wrap a
PooledDatasource rather than a driver. I couldn't find any when I started on
tranql :-) You should be able to make an AbstractPooledDatasourceMCF similar
to the AbstractXADatasourceMCF but using locat tx.
I don't think that only rejecting a few known exceptions is necessarily a good
idea. For the generic ra I implemented a new exception sorter that allows
exceptions with SQLCode from a list. However I suspect the list of non-fatal
SQLCOdes could be a lot more comprehensive. Can anyone find the list in the
ansi or x/open specs?
> Database pool unusable after database unavailable for awhile
> ------------------------------------------------------------
>
> Key: GERONIMO-4222
> URL: https://issues.apache.org/jira/browse/GERONIMO-4222
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Affects Versions: 2.0.2, 2.1.3, 2.1.4
> Environment: Red Hat Enterprise Linux Server v5.2
> WAS-CE v2.0.0.1, based on Geronimo v2.0.2
> Reporter: David Frahm
> Fix For: Wish List
>
> Attachments: before and after wasce restart.txt, PGtrial.patch,
> stacktrace.txt, tranql-connector-postgresql-common-1.1.jar
>
>
> I have frequent trouble with my database pool to an AS/400. The database is
> taken down every night for backup, and at least once a week the connection
> pool is unusable after the database comes back up. Restarting the connection
> pool makes everything work again.
> We are new to Geronimo/WAS-CE -- just this one app on one server -- so I
> don't have anything to compare to. However, we have had this same issue with
> a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are
> several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble.
> Configuration Info
> Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver)
> Pool Min Size: 0
> Pool Max Size: 100
> Blocking Timeout: 5000
> Idle Timeout: 15
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
