[Architecture] HikariCP as jdbc connection pool implementation for C5

Hi all, We are in the process of implementing data sources for C5. As the jdbc connection pool implementation we are hoping to use HikariCP [1]. For previous Carbon versions tomcat jdbc connection pooling is used as the connection pool implementation. The reasons behind migrating from tomcat conne

Re: [Architecture] HikariCP as jdbc connection pool implementation for C5

Hi All, Is there something compatible to "testWhileIdle" (DBCP/TomcatCP) in HikariCP ?, This is something which can be helpful to prevent connection pool exhaustion due to some firewall behaviour [1]. I think we need to add this in our wrapper, if it is not supported OOB in HikariCP. [1]https://gr

Re: [Architecture] HikariCP as jdbc connection pool implementation for C5

Hi Ruwan, HikariCP says that, they use the JDBC4's Connection#isValid method to check for connection liveness, where it seems to be a native way to check if connections are stale or not. This itself seems like a good improvement over the earlier mechanism used in DBCP/JDBC-Pool. Cheers, Anjana.