Bamboo upgrade to 7.2 or higher will keep the c3p0 configuration for historical reference

Still need help?

The Atlassian Community is here for you.

Ask the community

For Atlassian eyes only

This article is Not Validated and cannot be shared with customers.

Platform Notice: Server and Data Center Only. This article only applies to Atlassian products on the server and data center platforms.


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:

    <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>


Bamboo upgraded from a version below 7.2 to 7.2 or above.


It's safe to remove all properties starting with hibernate.c3p0 after successful upgrade to 7.2 or higher.

Last modified on Jun 7, 2022

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.