1 |
0c905a46
|
Andreas Kohlbecker
|
#
|
2 |
1690288d
|
Andreas Kohlbecker
|
# The CDM-Server instantiates the 3cp0 connection pools on behalf of the cdm-remote-webapp instances and passes
|
3 |
|
|
# the the connection pool per JNDI to the cdm-webapp instances. Thus we need to repeat the configuration as
|
4 |
|
|
# defined in cdmlib-persistence\src\main\resources\c3p0-config.xml
|
5 |
0c905a46
|
Andreas Kohlbecker
|
#
|
6 |
|
|
|
7 |
|
|
## idleConnectionTestPeriod:
|
8 |
|
|
# if this is a number greater than 0, c3p0
|
9 |
|
|
# will test all idle, pooled but unchecked-out connections, every this
|
10 |
|
|
# number of seconds
|
11 |
1690288d
|
Andreas Kohlbecker
|
# c3p0.idleConnectionTestPeriod = 60
|
12 |
0c905a46
|
Andreas Kohlbecker
|
|
13 |
1690288d
|
Andreas Kohlbecker
|
c3p0.testConnectionOnCheckout = true
|
14 |
|
|
|
15 |
|
|
## automatichoweverTestTable:
|
16 |
0c905a46
|
Andreas Kohlbecker
|
# If provided, c3p0 will create an
|
17 |
|
|
# empty table of the specified name, and use queries against that table
|
18 |
|
|
# to test the Connection. If automaticTestTable is provided, c3p0 will
|
19 |
|
|
# generate its own test query, therefore any preferredTestQuery set
|
20 |
|
|
# will be ignored. You should not work with the named table after c3p0
|
21 |
|
|
# creates it; it should be strictly for c3p0's use in testing your
|
22 |
|
|
# Connection.
|
23 |
|
|
c3p0.automaticTestTable = _c3p0ConnectionTest
|
24 |
|
|
|
25 |
1690288d
|
Andreas Kohlbecker
|
# explicitly telling c3p0 to use the log4j logging library
|
26 |
|
|
# see http://www.mchange.com/projects/c3p0/#configuring_logging
|
27 |
|
|
com.mchange.v2.log.MLog = log4j
|
28 |
|
|
|
29 |
|
|
# if you do not want c3p0 to register MBeans with your JMX environment, you can suppress JMX support entirely
|
30 |
|
|
# for some reason this is required for the cdm-server:
|
31 |
|
|
c3p0.management.ManagementCoordinator=com.mchange.v2.c3p0.management.NullManagementCoordinator
|