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

["Donald Woods (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Donald Woods updated GERONIMO-4222:
-----------------------------------

    Affects Version/s:     (was: 2.1.4)
                           (was: 2.1.2)
                           (was: 2.2)
                           (was: 2.1.1)
                           (was: 2.1)
        Fix Version/s:     (was: 2.0.4)
                           (was: 2.1.4)
                           (was: 2.2)
                       Wish List
             Assignee:     (was: Donald Woods)

User reported that there is no hang.  The lost connections are expected, unless you are using something like Oracle RAC which provides failover at the JDBC driver level.  Unassigning, in case anyone else wants to look into this, but Geronimo 2.0.3-SNAPSHOT, 2.1.x and 2.2 includes the udpated txmanager fixes required to enable failover support in the TranQL connectors.

> 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
>             Fix For: Wish List
>
>         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.