From 3705923e89946ea9d819d15406a1d74068fd0fc9 Mon Sep 17 00:00:00 2001 From: georgeangeletos Date: Tue, 20 May 2014 14:27:49 +0300 Subject: [PATCH] Update README.md Specified value of leakDetectionThreshold must be >= 10secs --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index cd12f2f3..a7dc9468 100644 --- a/README.md +++ b/README.md @@ -109,7 +109,8 @@ is disabled. While the default is 0, and other connection pool implementations leak detection is "not for production" as it imposes a high overhead, at least in the case of HikariCP the imposed overhead is only 5μs (*microseconds*) split between getConnection() and close(). Maybe other pools are doing it wrong, but feel free to use leak detection under -HikariCP in production environments if you wish. *Default: 0* +HikariCP in production environments if you wish. Lowest acceptable value for enabling leak +detection is 10000 (10 secs). *Default: 0* :negative_squared_cross_mark:``initializationFailFast``
This property controls whether the pool will "fail fast" if the pool cannot be seeded with