geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jack Cai (JIRA)" <>
Subject [jira] Updated: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
Date Wed, 16 Sep 2009 03:05:00 GMT


Jack Cai updated GERONIMO-4222:

    Attachment: PGtrial.patch

Attaching a modified trial patch that hard code the fatal error codes.

Even though this might fix the problem with Postgresql, it's far from the final solution.

I realize that tranql does not take advantange of the PooledDatasource/PooledConnection implemenations
that are available in most existing DBMS JDBC drivers. The PooledConnection can notify a listener
when a fatal error occured and the connection should be discarded. I'd suggest that we improve
tranql to use PooledDatasource, instead of relying on a customized ExceptionSorter that we
have to write by ourselves for every DBMS.

What do others think?

> Database pool unusable after database unavailable for awhile
> ------------------------------------------------------------
>                 Key: GERONIMO-4222
>                 URL:
>             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,
> 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 (
> 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.

View raw message