[
https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jack Cai updated GERONIMO-4222:
-------------------------------
Attachment: tranql-connector-mysql-local-1.3-SNAPSHOT.rar
vendors.patch
connector.patch
I've completed the patch that will leverage the PooledConnection interface, so
pasting it here for initial review.
The connector.patch is for the tranql-connector trunk, and the vendors.patch
contains updates to the mysql, derby and pg connectors (for convenience, I
created the patch from the vendor root.)
I'm uploading the built RAR packages so hopefully somebody can help to test the
new connectors. To test them with an existing Geronimo build, need to rename
the RAR package to match the version used in that Geronimo build.
> 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-mysql-local-1.3-SNAPSHOT.rar,
> tranql-connector-postgresql-common-1.1.jar, 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.
