You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm using hikariCP in productions. I am really appreciate for your efforts.
Recently, i experienced failing a pool initialization. the origin of the issue is from connection timeout.
In database high load, db connection was made by slow. I could increase hikari connectionTimeout but I do not want to increase wait time for pool.
Actually, i resolved this issue by setting a system property for driver specific connect timeout
ex) for oracle, -Doracle.net.CONNECT_TIMEOUT
But, for other databases, other properties should be used.
If hikariCP provide a separate property for loginTImeout, It will be convenient.
I know there is a method like com.zaxxer.hikari.HikariDataSource#setLoginTimeout. But it affect only in case that pool is already created.
Thank you!
The text was updated successfully, but these errors were encountered:
Hi, I'm using hikariCP in productions. I am really appreciate for your efforts.
Recently, i experienced failing a pool initialization. the origin of the issue is from connection timeout.
In database high load, db connection was made by slow. I could increase hikari connectionTimeout but I do not want to increase wait time for pool.
Actually, i resolved this issue by setting a system property for driver specific connect timeout
ex) for oracle,
-Doracle.net.CONNECT_TIMEOUT
But, for other databases, other properties should be used.
If hikariCP provide a separate property for loginTImeout, It will be convenient.
I know there is a method like
com.zaxxer.hikari.HikariDataSource#setLoginTimeout
. But it affect only in case that pool is already created.Thank you!
The text was updated successfully, but these errors were encountered: