-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Medium
-
Affects Version/s: 6.6.5, 6.8.2, 6.13.4, 6.15.7, 7.0.1
-
Component/s: Server - Platform
-
None
-
10
-
Severity 2 - Major
-
6
Background
When Confluence starts up, it created 2 connection pools.
Steps to reproduce
- Start Confluence
- Launch jconsole
- Connect to Confluence
- Go to MBeans tab and look at com.mchange.v2.c3p0
Technical details
This issue happens only when StartupSchemaChecker.checkSchema is called. In this case an additional connection pool is created. This connection pool uses Hibernate5 without Hibernate2 adapter.
When build numbers in the home folder and in the DB are different, StartupSchemaChecker.checkSchema is not called, and the second pool is not created.
- is related to
-
CONFSERVER-58053 Setting c3p0.min_size to a non-zeroed value causes Confluence to trigger an overhead of Database Connections
-
- Closed
-