[
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-postgresql-common-1.1.jar
As David pointed out, there's no stardard way to tell that an SQLException is
fatal. So it might be hard to make the generic adapter detect dead connection.
I went out writing an exception sorter that will regard the following SQL
states as fatal for Postgresql. The list of fatal errors can be configured
through the property file packaged in the attached jar. Does anybody want to
test it with Geronimo (simply replace this jar with the one in Geronimo repo)?
CONNECTION_UNABLE_TO_CONNECT: 08001
CONNECTION_DOES_NOT_EXIST: 08003
CONNECTION_REJECTED: 08004
CONNECTION_FAILURE: 08006
CONNECTION_FAILURE_DURING_TRANSACTION: 08007
PROTOCOL_VIOLATION: 08P01
COMMUNICATION_ERROR: 08S01
SYSTEM_ERROR: 60000
> 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, 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.
