A connection pooling question on the users list prompted me to write a short history [1] of Tomcat's connection pooling with respect to DBCP 1, DBCP 2 and tomcat-jdbc. That got me thinking.
Given the current situation: - DBCP 2 is stable - The Commons community is supporting DBCP 2 - tomcat-jdbc is stable - support for tomcat-jdbc is sporadic at best - DBCP 2 performance is very close to that of tomcat-jdbc (to be clear, tomcat-jdbc still has better performance) I'd like to propose that we do not ship tomcat-jdbc with Tomcat 9 onwards (i.e. remove it from trunk/modules). There are some features in tomcat-jdbc that are not available in Commons DBCP 2. This proposal includes porting those features to DBCP 2 if there is user demand for them. Thoughts? Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
