Bamboo upgrade to 7.2 or higher will keep the c3p0 configuration for historical reference
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
In Bamboo 7.2 HikariCP replaces C3p0 as database connection pool manager and the C3p0 properties in bamboo.cfg.xml are no longer used.
The old configuration will not be removed after the upgrade for historical reference.
Example of bamboo.cfg.xml after upgrade:
<application-configuration>
<setupStep>complete</setupStep>
<setupType>custom</setupType>
<buildNumber>80110</buildNumber>
<properties>
....
<property name="hibernate.c3p0.acquire_increment">3</property>
<property name="hibernate.c3p0.idle_test_period">30</property>
<property name="hibernate.c3p0.max_size">300</property>
<property name="hibernate.c3p0.max_statements">0</property>
<property name="hibernate.c3p0.min_size">30</property>
<property name="hibernate.c3p0.timeout">120</property>
......
<property name="hibernate.hikari.idleTimeout">120000</property>
<property name="hibernate.hikari.maximumPoolSize">300</property>
<property name="hibernate.hikari.minimumIdle">30</property>
<property name="hibernate.hikari.registerMbeans">true</property>
<property name="hibernate.setup">true</property>
......
</properties>
</application-configuration>Environment
Bamboo upgraded from a version below 7.2 to 7.2 or above.
Solution
It's safe to remove all properties starting with hibernate.c3p0 after successful upgrade to 7.2 or higher.