H2 Connection leaks in application logs

[Tapan Aggarwal]

There is high H2 Connection leak  detection count we are recieving and Connection pool active count if set higher to 800, the application does not release this Connection pool to 0 even minutes after high load test ends and available H2 count is 0 all through than. We have to restart the instance to make them 0 . We are using Quarkus framework, Please see attached graphs.

These are the rest of h2 jdbc properties in quarkus application properties file :

quarkus.datasource.jdbc.min-size=400

quarkus.datasource.jdbc.max-size=800

quarkus.datasource.jdbc.detect-statement-leaks=true

quarkus.datasource.jdbc.pooling-enabled=true

[Noel Grandin]

somewhere you are leaking connections i.e. forgetting to return them to the pool