|
|
|
@ -170,11 +170,11 @@ of 0 means that idle connections are never removed from the pool. The minimum a
|
|
|
|
|
⌚``keepaliveTime``<br/>
|
|
|
|
|
This property controls how frequently HikariCP will attempt to keep a connection alive, in order to prevent
|
|
|
|
|
it from being timed out by the database or network infrastructure. This value must be less than the
|
|
|
|
|
`maxLifetime` value. A "keepalive" will only occur on idle connections. When the time arrives for a "keepalive"
|
|
|
|
|
`maxLifetime` value. A "keepalive" will only occur on an idle connection. When the time arrives for a "keepalive"
|
|
|
|
|
against a given connection, that connection will be removed from the pool, "pinged", and then returned to the
|
|
|
|
|
pool. The 'ping' is one of either invocation of the JDBC4 `isValid()` method, or execution of the
|
|
|
|
|
pool. The 'ping' is one of either: invocation of the JDBC4 `isValid()` method, or execution of the
|
|
|
|
|
`connectionTestQuery`. Typically, the duration out-of-the-pool should be measured in single digit milliseconds
|
|
|
|
|
or even sub-milliseconds, and therefore should have little or no noticible performance impact. The minimum
|
|
|
|
|
or even sub-millisecond, and therefore should have little or no noticible performance impact. The minimum
|
|
|
|
|
allowed value is 30000ms (30 seconds), but a value in the range of minutes is most desirable.
|
|
|
|
|
*Default: 0 (disabled)*
|
|
|
|
|
|
|
|
|
|