Managing Database Connection Pool Settings for Content Manager
With pooled connections, Content Manager does not have to create and open connections for new requests. This provides faster response times. However, pooled connections reserve database resources, so idle connections should be closed if they are not needed.
You can manage the number of connections to the content store by limiting the maximum number of connections and by specifying how long connections stay in the pool before they are automatically closed.
The following parameters are available:
- CM.DbConnectPoolMax
Specifies the maximum number of concurrent database connections that the content store allows.
This parameter applies only to the Content Manager connection pool settings. If you have other services that access the same content store, there may be more concurrent database connections than specified in this parameter.
The valid settings are -1, or 5 to 2147483647, or the database setting, whichever is less. The default is -1 (unlimited).
- CM.DbConnectPoolTimeout
Specifies in milliseconds the maximum length of time that a thread waits for a connection to be available from the pool.
The valid settings are -1 to 2147483627. A setting of 0 specifies that threads never wait for a connection if one is not available immediately. The default is -1 (unlimited).
- CM.DbConnectPoolIdleTime
Specifies in milliseconds the minimum length of time that a connection stays idle in the pool. This parameter is used only if the value of the DbConnectPoolCleanUpPeriod setting is positive.
The valid settings are -1 to 2147483647. A setting of 0 or -1 specifies that idle connections are closed when Content Manager restarts. The default is 300000 (5 min).
- CM.DbConnectPoolCleanUp Period
Specifies in milliseconds the length of time between invocations of a cleanup thread that closes idle connections in the pool that exceed the setting of DbConnectPoolIdleTime.
The valid settings are -1 to 2147483647. The default is 300000 (5 min).