From: Andreas Kohlbecker <a.kohlbecker@bgbm.org>
Date: Tue, 12 Mar 2019 07:53:12 +0000 (+0100)
Subject: notes on commented settings regarding debugging of leaky db connections
X-Git-Tag: 5.6.0^2~5
X-Git-Url: https://dev.e-taxonomy.eu/gitweb/cdm-server.git/commitdiff_plain/df8414669509254afa7d6d35f85f1528d1c5c978

notes on commented settings regarding debugging of leaky db connections
---

diff --git a/src/main/resources/c3p0.properties b/src/main/resources/c3p0.properties
index be02bf0..983c292 100644
--- a/src/main/resources/c3p0.properties
+++ b/src/main/resources/c3p0.properties
@@ -47,11 +47,11 @@ c3p0.minPoolSize = 1
 #c3p0.maxConnectionAge = 600
 
 # maxIdleTime 10800 = 3 hours
-c3p0.maxIdleTime = 600
+c3p0.maxIdleTime = 10800
 
 c3p0.maxIdleTimeExcessConnections = 300
 
-## automatichoweverTestTable: 
+## automaticTestTable: 
 #			If provided, c3p0 will create an
 #			empty table of the specified name, and use queries against that table
 #			to test the Connection. If automaticTestTable is provided, c3p0 will
@@ -65,7 +65,8 @@ c3p0.automaticTestTable = _c3p0ConnectionTest
 # The ManagementCoordinator was causing problems in the past but seem to be ok now.
 #c3p0.management.ManagementCoordinator=com.mchange.v2.c3p0.management.NullManagementCoordinator
 
-
-
-c3p0.debugUnreturnedConnectionStackTraces=true
-c3p0.unreturnedConnectionTimeout=30
+# The below settings should only be used to debug connection leaks
+# make sure the logging level for com.mchange.v2 is at least at INFO
+# see https://dev.e-taxonomy.eu/redmine/projects/edit/wiki/DebugC3P0Connections for details
+#c3p0.debugUnreturnedConnectionStackTraces=true
+#c3p0.unreturnedConnectionTimeout=30