[jira] Issue Comment Edited: (GERONIMO-4222) Database pool unusable after database unavailable for awhile

["Thad West (JIRA)" <ji...@apache.org>]

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

swisst edited comment on GERONIMO-4222 at 8/5/08 9:22 AM:
-------------------------------------------------------------

We are running Geronimo 2.0.2 connecting to MySQL v5

The default for MySQL is to close a connection after 8 hours of inactivity (overnight for us).  Here are the details:
http://dev.mysql.com/doc/refman/5.0/en/gone-away.html

For testing purposes, you could change the time limit by setting the wait_timeout variable when you start mysql.
http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html#option_mysqld_wait_timeout

So...MySQL invalidates the connection, but Geronimo keeps it in the pool.  As soon as you get one of these connections and try to use it, kablammo!

      was (Author: swisst):
    We are running Geronimo 2.0.2 connecting to MySQL v5

The default for MySQL is to close a connection after 8 hours of inactivity (overnight for us).  Here are the details:
http://dev.mysql.com/doc/refman/5.0/en/gone-away.html

For testing purposes, you could change the time limit by setting the wait_timeout variable when you start mysql.
http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html

So...MySQL invalidates the connection, but Geronimo keeps it in the pool.  As soon as you get one of these connections and try to use it, kablammo!
  
> 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: 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.