Bug 56970 - MaxActive vs. MaxTotal for commons-dbcp and tomcat-jdbc-pool in tomcat 8
Summary: MaxActive vs. MaxTotal for commons-dbcp and tomcat-jdbc-pool in tomcat 8
Status: NEW
Alias: None
Product: Tomcat Modules
Classification: Unclassified
Component: jdbc-pool (show other bugs)
Version: unspecified
Hardware: PC Mac OS X 10.4
: P2 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-11 20:50 UTC by Jake Landis
Modified: 2014-09-12 11:45 UTC (History)
0 users


Attachments
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 Jake Landis 2014-09-11 20:50:26 UTC 
http://tomcat.apache.org/migration-8.html#Database_Connection_Pooling

Documents: The maxActive configuration option has been renamed to maxTotal

http://tomcat.apache.org/tomcat-8.0-doc/jdbc-pool.html

Documents: (int) The maximum number of active connections that can be allocated from this pool at the same time. The default value is 100

There is no mention of maxTotal, and observation (via JMX) appears as though the default is 8 , not 100.
Comment 1 Konstantin Kolinko 2014-09-12 11:45:07 UTC 
> http://tomcat.apache.org/migration-8.html#Database_Connection_Pooling
> Documents: The maxActive configuration option has been renamed to maxTotal

The above documentation talks about DBCP pool.

> http://tomcat.apache.org/tomcat-8.0-doc/jdbc-pool.html

The above documentation page is about JDBC pool.


The "Common Attributes" table on JDBC pool page can be improved. It talks about comparing the tomcat-jdbc pool with commons-dbcp, but Tomcat 8 is bundled with commons-dbcp2.