[
https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757852#action_12757852
]
David Jencks commented on GERONIMO-4222:
----------------------------------------
Jack, I was working on the sqlstate exception sorter and just implemented
ConnectionPoolDataSource wrapping before I saw your work. I'll compare our
approaches and look at the vendor wrappers tomorrow.
Radim, I haven't looked into this in a long time, but I think that the
standard behavior for uncommitted work when putting a connection back in the
pool is to commit it. However, the problem we are dealing with here is that on
a connection error, after removing the connection from the pool so it won't be
used ever again, we are not trying to rollback work on it before destroying it.
If we could tell if the connection was actually still usable, we wouldn't
close it at all if the rollback could succeed... so two things to do are to
improve our decision of when to close the connection (using a
ConnectionPoolDataSource, and a better ExceptionSorter) and trying to rollback
before destroy just in case we were wrong about needing to destroy the
connection.
> 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
> Assignee: Jack Cai
> Fix For: Wish List
>
> Attachments: before and after wasce restart.txt, connector.patch,
> PGtrial.patch, stacktrace.txt,
> tranql-connector-derby-embed-local-1.5-SNAPSHOT.rar,
> tranql-connector-derby-embed-xa-1.5-SNAPSHOT.rar,
> tranql-connector-mysql-local-1.3-SNAPSHOT.rar,
> tranql-connector-mysql-xa-1.3-SNAPSHOT.rar,
> tranql-connector-postgresql-common-1.1.jar,
> tranql-connector-postgresql-local-1.2-SNAPSHOT.rar,
> tranql-connector-postgresql-xa-1.2-SNAPSHOT.rar, vendors.patch
>
>
> 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.
