geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Frahm (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
Date Mon, 11 Aug 2008 21:12:44 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621606#action_12621606
] 

dfrahm@teamhuber.com edited comment on GERONIMO-4222 at 8/11/08 2:11 PM:
----------------------------------------------------------------

This log shows the connection errors, then a server restart and everything is happy again.

Its not the 'called with null' error that I was remembering, but that might be because of
one of the following:

1.) The server was upgraded from 1.x to 2.x around that time, so maybe the error changed
2.) I think the 'top-level' error is a bit different when caused by one of my JSF components;
The errors in this attachment are from a standard j_security_check form authentication.

      was (Author: dfrahm@teamhuber.com):
    This log shows the connection errors, then a server restart and everything is happy again.
  
> 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
>         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 (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.


Mime
View raw message