geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thad West (JIRA)" <>
Subject [jira] Issue Comment Edited: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
Date Tue, 12 Aug 2008 16:04:44 GMT


swisst edited comment on GERONIMO-4222 at 8/12/08 9:03 AM:

The Derby test case outlined by David sounds like a good idea.  However, I don't think the
DB should be deleted.  

The problem, as I see it, is how does the connection pool respond to stale connections.  If
the DB is deleted, then I see no other reasonable alternative except for the pool to throw
an exception.  

However, if there is a connection timeout setting in Derby (like I outlined for MySQL...see
my first comment), that would be the more accurate test.  The database still needs to be available,
the connections in the pool should be invalidated by the DB Engine.  The Geronimo pool should
gracefully recover from stale connections and get another connection.

      was (Author: swisst):
    The Derby test case outlined by David would sufficiently recreate the problem I have encountered!
> 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
>         Environment: Red Hat Enterprise Linux Server v5.2
> WAS-CE v2.0.0.1, based on Geronimo v2.0.2
>            Reporter: David Frahm
>         Attachments: before and after wasce restart.txt, 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