I've recently become aware of the new-ish tomcat connection pool (http://people.apache.org/~fhanik/jdbc-pool/) which appears to be at version 1.0.8.5 (a January 2010 release?).
Before I recommend we begin using this in a production situation, I'd like to gather a bit of data on it. As a bit of background, we're migrating off of Weblogic server to Tomcat (simplification!), but one of the things we have been very happy with in Weblogic is the robust connection pool management. We have some environments in which we use "multipools", some where we connect to Oracle RAC and some where we use Oracle's Fast Start Failover to transparently (to the application) cut over to a standby database at the connection pool level in an extremely short amount of time (compared to modifying connection descriptors and bouncing a farm of servers). I started by researching available connection pools for tomcat, and it seems most folks either use DBCP (which has a host of issues) or C3PO (which has its own issues, including that it is LGPL licensed). The "feature page" of the tomcat connection pool (http://people.apache.org/~fhanik/jdbc-pool/jdbc-pool.html) seems quite promising, but to be honest, it concerns me that the module is only readily available from a commiter's pages or from source. 1) Is the tomcat community committed to this new module? (We've been burned by too many abandoned FOSS projects to discount this issue) 2) When will it be available as a standard tomcat module? 3) Is it considered "released" or still in a beta stage (I found the beta announcement from 2008)? 4) Although I don't see anything like multipools, are there any plans to support something like them? Could they be implemented within the interceptor framework? 5) What are the implications for using with RAC? 6) What are the implications for using with FSF (Fast Start Failover)? 7) What are the implications for using within and XA environment (though we work hard to avoid XA it's important to know of any limitations etc)? Thanks! Jason Pringle This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp
