View | Details | Raw Unified | Return to bug 57587
Collapse All | Expand All

(-)webapps/docs/jndi-datasource-examples-howto.xml (-7 / +9 lines)
Lines 163-177 Link Here
163
163
164
<p>
164
<p>
165
To configure a DBCP DataSource so that abandoned database connections are
165
To configure a DBCP DataSource so that abandoned database connections are
166
removed and recycled add the following attribute to the
166
removed and recycled, add one or both of the following attributes to the
167
<code>Resource</code> configuration for your DBCP DataSource:
167
<code>Resource</code> configuration for your DBCP DataSource:
168
</p>
168
</p>
169
169
<source>removeAbandonedOnBorrow=true</source>
170
<source>removeAbandoned="true"</source>
170
<source>removeAbandonedOnMaintenance=true</source>
171
171
<p> The default for both of these attributes is <code>false</code>.  Note that 
172
<p>
172
<code>removeAbandonedOnMaintenance</code> has no effect unless pool 
173
When available database connections run low DBCP will recover and recycle
173
maintenance is enabled by setting <code>timeBetweenEvictionRunsMillis</code> 
174
any abandoned database connections it finds. The default is <code>false</code>.
174
to a positive value.  See the 
175
<a href="http://commons.apache.org/dbcp/configuration.html">
176
DBCP documentation</a> for full documentation on these attributes.
175
</p>
177
</p>
176
178
177
<p>
179
<p>

Return to bug 57587