-
Type:
Regression Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 7.0.0 Beta 6
-
Fix Version/s: 7.0.0 Beta 6
-
Component/s: Environments, Environments > Databases
-
Labels:None
-
Fix Priority:2
-
Git Pull Request:
HikariCP is the default connection pool, not C3PO. Update portal.properties to reflect this.
# # Liferay can use C3PO, DBCP, or Tomcat for connection pooling. See # com.liferay.portal.dao.jdbc.util.DataSourceFactoryBean for the actual # implementation. It is important to understand the strengths and weaknesses # of each provider so that you can choose the best one that fits your # deployment scenario. Provider specific properties can also be passed along # directly to the provider. For example, the property # "jdbc.default.acquireIncrement" is read by C3PO, and the property # "jdbc.default.maxActive" is read by DBCP. # # The default provider is C3PO. # #jdbc.default.liferay.pool.provider=c3po #jdbc.default.liferay.pool.provider=dbcp jdbc.default.liferay.pool.provider=hikaricp #jdbc.default.liferay.pool.provider=tomcat