On 09/23/2010 2:27 PM, Mark Thomas wrote: > Several release attempts have failed due to a lack of interest.
Lack of interest by whom? The development team or the tomcat community? > That said, $work is using this as the default pool in a commercial > product based on Tomcat with minimal issues. Ah yes, I do see that jar file in a commercial tomcat I downloaded recently..... > Overall, I'd suggest you take another look at DBCP. The historical > issues with deadlocks have been fixed and syncs reduced to the bare > minimum. jdbc-pool will easily beat it for performance in highly > concurrent apps running on multi-core servers but apart from that, DBCP > and jdbc-pool are pretty comparable and there are a number of areas > where DBCP does a better job of making the pooled connection look like > a > normal connection. There are a few places where jdbc-pool requires > extra > (user written) interceptors to do this. Will do > The next generation of DBCP will be based on Pool 2.0 which will be > based on the Java 5 concurrency features. Current thinking is to > 'borrow' code from jdbc-pool to update Commons Pool but that work has > not been started. Ah - a roadmap :) Is there some chatter on the dev list to read up on here? 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 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
