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