[
https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758103#action_12758103
]
Jack Cai commented on GERONIMO-4222:
------------------------------------
Thanks Forrest for trying out the patch!
Guess the problem is because you still have some tranql-connector-1.4.jar in
your repo which get loaded by the server (each vendor RAR contains a copy of
this jar). Once we replace all the 1.4 jars with the updated jars, the problem
shall go away.
> 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.
