Project

General

Profile

Download (1.81 KB) Statistics
| Branch: | Tag: | Revision:
1
#
2
# 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
#
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
# For some applications, high performance is more important than the risk of an 
14
# occasional database exception. In its default configuration, c3p0 does no 
15
# Connection testing at all. Setting a fairly long idleConnectionTestPeriod, and 
16
#  not testing on checkout and check-in at all is an excellent, high-performance 
17
# approach. 
18
#
19

    
20
c3p0.idleConnectionTestPeriod = 120
21
c3p0.testConnectionOnCheckout = false
22
c3p0.testConnectionOnCheckin = false
23
c3p0.maxConnectionAge = 600
24
c3p0.maxIdleTime = 300
25
c3p0.maxIdleTimeExcessConnections = 200
26
c3p0.minPoolSize = 1
27

    
28
## automatichoweverTestTable: 
29
#			If provided, c3p0 will create an
30
#			empty table of the specified name, and use queries against that table
31
#			to test the Connection. If automaticTestTable is provided, c3p0 will
32
#			generate its own test query, therefore any preferredTestQuery set
33
#			will be ignored. You should not work with the named table after c3p0
34
#			creates it; it should be strictly for c3p0's use in testing your
35
#			Connection.
36
c3p0.automaticTestTable = _c3p0ConnectionTest
37

    
38
# if you do not want c3p0 to register MBeans with your JMX environment, you can suppress JMX support entirely
39
# for some reason this is required for the cdm-server:
40
#c3p0.management.ManagementCoordinator=com.mchange.v2.c3p0.management.NullManagementCoordinator
(1-1/3)