Author: markt
Date: Tue Feb 17 11:43:46 2015
New Revision: 1660353
URL: http://svn.apache.org/r1660353
Log:
Update for DBCP2.
Patch provided by Phil Steitz
Modified:
tomcat/trunk/webapps/docs/jndi-datasource-examples-howto.xml
Modified: tomcat/trunk/webapps/docs/jndi-datasource-examples-howto.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/jndi-datasource-examples-howto.xml?rev=1660353&r1=1660352&r2=1660353&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/jndi-datasource-examples-howto.xml (original)
+++ tomcat/trunk/webapps/docs/jndi-datasource-examples-howto.xml Tue Feb 17
11:43:46 2015
@@ -163,15 +163,17 @@ which opened these resources and never c
<p>
To configure a DBCP DataSource so that abandoned database connections are
-removed and recycled add the following attribute to the
+removed and recycled, add one or both of the following attributes to the
<code>Resource</code> configuration for your DBCP DataSource:
</p>
-
-<source>removeAbandoned="true"</source>
-
-<p>
-When available database connections run low DBCP will recover and recycle
-any abandoned database connections it finds. The default is <code>false</code>.
+<source>removeAbandonedOnBorrow=true</source>
+<source>removeAbandonedOnMaintenance=true</source>
+<p> The default for both of these attributes is <code>false</code>. Note that
+<code>removeAbandonedOnMaintenance</code> has no effect unless pool
+maintenance is enabled by setting <code>timeBetweenEvictionRunsMillis</code>
+to a positive value. See the
+<a href="http://commons.apache.org/dbcp/configuration.html";>
+DBCP documentation</a> for full documentation on these attributes.
</p>
<p>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
