From aa76f275668391fafdc4201f418c09485d04b246 Mon Sep 17 00:00:00 2001 From: Brett Wooldridge Date: Mon, 25 Jan 2021 00:52:31 +0900 Subject: [PATCH] Update README.md --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index f2792bf2..1957ff46 100644 --- a/README.md +++ b/README.md @@ -170,11 +170,11 @@ of 0 means that idle connections are never removed from the pool. The minimum a ⌚``keepaliveTime``
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)*