Summary

On a fresh install of Confluence 6.1.x, we get warnings during the startup that the c3p0 properties are being ignored and the Hibernate built-in connection pool will be used instead.

Environment

• Confluence 6.1.x

Steps to Reproduce

1. Fresh install
2. Restart the application
3. Tail the atlassian-confluence.log

Expected Results

No warning is shown and c3p0 properties are applied.

Actual Results

The following warnings are printed:

2017-04-18 10:11:51,380 WARN [AtlassianEvent::CustomizableThreadFactory-4] [jdbc.connections.internal.ConnectionProviderInitiator] instantiateC3p0Provider HHH000022: c3p0 properties were encountered, but the c3p0 provider class was not found on the classpath; these properties are going to be ignored.
2017-04-18 10:11:51,386 WARN [AtlassianEvent::CustomizableThreadFactory-4] [hibernate.orm.connections.pooling] configure HHH10001002: Using Hibernate built-in connection pool (not for production use!)

Notes

After a deeper analysis, we identified that the warnings are harmless and are caused by a schema check before the complete startup of Hibernate. With that said, after the check and the complete startup of Hibernate, the c3p0 properties are successfully applied so we can safely ignore the warnings.

Workaround

No known workaround at the moment.