|
1
|
#
|
|
2
|
# The CDM-Server intatiates the 3cp0 connection pools on behalf of the cdm-remote-webapp insances and passes
|
|
3
|
# the the connection pool per JNDI to the webapps. Thus we need to repeat the configuration as defined in
|
|
4
|
# cdmlib-persistence\src\main\resources\c3p0-config.xml
|
|
5
|
#
|
|
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
|
c3p0.idleConnectionTestPeriod = 60
|
|
12
|
|
|
13
|
## automaticTestTable:
|
|
14
|
# If provided, c3p0 will create an
|
|
15
|
# empty table of the specified name, and use queries against that table
|
|
16
|
# to test the Connection. If automaticTestTable is provided, c3p0 will
|
|
17
|
# generate its own test query, therefore any preferredTestQuery set
|
|
18
|
# will be ignored. You should not work with the named table after c3p0
|
|
19
|
# creates it; it should be strictly for c3p0's use in testing your
|
|
20
|
# Connection.
|
|
21
|
c3p0.automaticTestTable = _c3p0ConnectionTest
|
|
22
|
|
|
23
|
# however one additinal setting is required
|
|
24
|
com.mchange.v2.c3p0.management.ManagementCoordinator=com.mchange.v2.c3p0.management.NullManagementCoordinator
|