geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Frahm (JIRA)" <>
Subject [jira] Commented: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
Date Tue, 12 Aug 2008 14:52:44 GMT


David Frahm commented on GERONIMO-4222:

I will see about trying a newer WASCE.  Might not happen very soon though.

I was trying to think about how to create a test case for this that doesn't involve our production
as/400.  With other people having this issue, maybe we could use a different database.

Certainly MySQL would be better, but what about something like Derby for a unit test?  That
could be embedded and therefore run with every build.  Maybe the test could:

1. initialize Derby, create the database, a table, some data
2. use the connection pool to access the data
3. take down Derby (even delete the database?)
4. repeat step 1
5. test the connection pool

I'm not sure what would be best, trying to debug the production issues or trying to create
a repo test case.  I guess I'll keep thinking on both and see which one yields some results.

> 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