I suggest you read this page and watch the attached video. The Oracle Performance Group demonstrates how an application with a pool of 96 connection easily handles 10,000 front-end users and 20,000 transactions per-second. PostgreSQL recommends a formula of: connections = ((core_count * 2) + effective_spindle_count) Where core_count is CPU cores, and effective_spindle_count is the … Read more
You’re using a recent version of Hikari CP and the connection leak resolves by itself (as visible in your logs). As noted by @M. Deinum the issue can be caused in a low value of hikari.leakDetectionThreshold property (your “in” query can take much more than 2 seconds). Try to increase it to 60000, then do … Read more
Declaring your own DataSource will already have implicity disabled Spring Boot’s auto-configuration of a data source. In other words this won’t be having any effect: @EnableAutoConfiguration(exclude = {DataSourceAutoConfiguration.class}) I think the problem lies in the fact that you aren’t binding Hikari-specific configuration to your MySQL DataSource. You need to do something like this: @Bean @Primary … Read more
As with most connection pools, Hikari doesn’t give you an actual JDBC Connection when you ask for one. What it does instead is give you a proxy that implements the Connection interface. In the case of Hikari – it’s a ConnectionProxy object. This proxy serves a few purposes, the main of which is – take … Read more
If you have springboot and you want logging your HikariCP parameters to check that the application has taken the configurations correctly put this in your application.yaml or application.properties logging.level.com.zaxxer.hikari.HikariConfig=DEBUG logging.level.com.zaxxer.hikari=TRACE Console will show you all
We recently had this issue, but the Connection Pool Error message was eventually just baiting. The real problem was a third-party system that did not accept more messages, thus blocking each thread. The connection never returned to the Pool if the thread had previously acquired a Connection from HikariCP. Hence, we had as many successful … Read more
There are a few issues with that URL and a latest PSQL driver may complain. jdbc:postgres: should be replaced with jdbc:postgresql: Do not use jdbc:postgresql://<username>:<passwor>…, user parameters instead: jdbc:postgresql://<host>:<port>/<dbname>?user=<username>&password=<password> In some cases you have to force SSL connection by adding sslmode=require parameter So your URL should be: jdbc:postgresql://@pellefant.db.elephantsql.com:5432/cwkqmdql?user=cwkqmdql&password=SsVqwdLxQObgaJAYu68O-8gTY1VmS9LX or jdbc:postgresql://@pellefant.db.elephantsql.com:5432/cwkqmdql?user=cwkqmdql&password=SsVqwdLxQObgaJAYu68O-8gTY1VmS9LX&sslmode=require I hope that will help.
Your database is not obtaining connection within (30000 milliseconds that is default connectionTimeout property) because of network latency or some of the queries which are taking too long to execute(more than 30000 milliseconds). Please try to increase value of property connectionTimeout. YML configuration example: spring: datasource: hikari: minimumIdle: 2 maximumPoolSize: 10 idleTimeout: 120000 connectionTimeout: 300000 … Read more
The problem is that the default value of the spring.datasource.hikari.maxLifetime property (default of 30 minutes, https://github.com/brettwooldridge/HikariCP#gear-configuration-knobs-baby) is higher than the database’s wait_timeout, 10 minutes in my case. So you have two options, either decrease the hikari.maxLifetime below 10 minutes, or increase the database’s wait_timeout property.
you need to write this structure on your bean configuration (this is your datasource): <bean id=”hikariConfig” class=”com.zaxxer.hikari.HikariConfig”> <property name=”poolName” value=”springHikariCP” /> <property name=”connectionTestQuery” value=”SELECT 1″ /> <property name=”dataSourceClassName” value=”${hibernate.dataSourceClassName}” /> <property name=”maximumPoolSize” value=”${hibernate.hikari.maximumPoolSize}” /> <property name=”idleTimeout” value=”${hibernate.hikari.idleTimeout}” /> <property name=”dataSourceProperties”> <props> <prop key=”url”>${dataSource.url}</prop> <prop key=”user”>${dataSource.username}</prop> <prop key=”password”>${dataSource.password}</prop> </props> </property> </bean> <!– HikariCP configuration –> <bean … Read more