Bug 57587 - JNDI Datasource HOW-TO refers to obsolete DBCP config property
Summary: JNDI Datasource HOW-TO refers to obsolete DBCP config property
Status: RESOLVED FIXED
Alias: None
Product: Tomcat 8
Classification: Unclassified
Component: Documentation (show other bugs)
Version: 8.0.x-trunk
Hardware: PC Mac OS X 10.1
: P5 normal (vote)
Target Milestone: ----
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-17 00:16 UTC by Phil Steitz
Modified: 2015-02-17 13:44 UTC (History)
0 users


Attachments
Update to use the new properties. (1.25 KB, patch)
2015-02-17 00:16 UTC, Phil Steitz 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Phil Steitz 2015-02-17 00:16:51 UTC 
Created attachment 32484 [details]
Update to use the new properties.

The DBCP example in the JNDI Datasource HOW-TO refers to the removeAbandoned property, which in DBCP2 has been replaced by removeAbandonedOnBorrow and removeAbandonedOnMaintenance.
Comment 1 Konstantin Kolinko 2015-02-17 11:54:19 UTC 
When did it happen? The DBCP documentation [1] mentions "removeAbandoned", but none of those two other properties?

One also needs to update the migration guide. [2]



[1] http://commons.apache.org/proper/commons-dbcp/configuration.html
[2] http://tomcat.apache.org/migration-8.html#Database_Connection_Pooling
Comment 2 Phil Steitz 2015-02-17 13:42:25 UTC 
This is since DBCP 2.0.  The DBCP config doc has been updated in trunk.  Changes will appear on the web site once the release in progress completes.
Comment 3 Mark Thomas 2015-02-17 13:44:31 UTC 
Fixed in trunk and 8.0.x for 8.0.21 onwards.