As part of the Tomcat 7.0 to Tomcat 8.0 version shift maxActive was replaced by maxTotal. Our portal.properties file continues to list maxActive which means that our customers using Tomcat as their connection pool handler are performance tuning with the incorrect property.
To my current understanding this only impacts customers tell Liferay to use Tomcat as their connection pool handler, such as with jdbc.default.jndi.name=jdbc/LiferayPool
Tomcat 8, as well as Tomcat 7, is shipped with two implementations of a database connection pool. The first implementation (the default one; though technically this can be changed via javax.sql.DataSource.Factory system property) is a copy of Apache Commons DBCP 2.x project, renamed to a different package…
There are a number of notable changes between Apache Commons DBCP 1.x (used by Tomcat 7 and earlier) and Apache Commons DBCP 2.x which are likely to require configuration changes.
The maxActive configuration option has been renamed to maxTotal
1.Navigate to the Liferay bundle’s directory
2. Navigate to /liferay_home/tomcat_home/ROOT/WEB-INF/lib/
3. Open portal-impl.jar
4. Open portal.properties
5. Search for “maxActive”
Expected Result: maxTotal should be listed alongside maxActive in some capacity so that customers who use Tomcat as their database connection pool handler are not forced to use the default maxTotal=8 while our default is maxActive=100
Actual Result: maxActive is listed, which only works for Tomcat 7.0. On bundles running on Tomcat 8.0 the default value is used (maxTotal=8)