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
If I understand the behavior correctly, there is an error in the javadoc for HikariConfig.setInitializationFailTimeout(); more specifically, the section describing behavior for negative timeout value:
A value less than zero will <i>not</i> bypass any connection attempt and
validation during startup, and therefore the pool will start immediately. The
pool will continue to try to obtain connections in the background. This can mean
that callers to {@code DataSource#getConnection()} may encounter exceptions.
It is my understanding that if timeout is less than zero connection initialization and validation during startup will be bypassed, so the <i>not</i> part should be removed.
The text was updated successfully, but these errors were encountered:
Environment
Problem description
If I understand the behavior correctly, there is an error in the javadoc for
HikariConfig.setInitializationFailTimeout()
; more specifically, the section describing behavior for negative timeout value:It is my understanding that if timeout is less than zero connection initialization and validation during startup will be bypassed, so the
<i>not</i>
part should be removed.The text was updated successfully, but these errors were encountered: