Controlling persistent back-end sessions

This setting controls how many back-end sessions the server keeps for each database regardless the idle period. The purpose of this setting is to reduce the warm-up time for an idle database. This setting ensures that several back-end sessions are available to handle increased demand. When the CCM server is first started, it does not automatically start this number of back-end sessions unless there is sufficient demand. However, after the number of back-end sessions reaches this value, that number persists.

Procedure

To change the server configuration:

  1. Stop the server.
  2. To change this value for all databases, modify the cm.webserver.persistent.sessions value in the ccm.server.properties file.
  3. To set a different value for a specific database, create a key called cm.webserver.persistent.sessions.database name in the ccm.server.properties file, and then assign the new value.
  4. Restart the server so that the changed values take effect.

Example

Examples for setting database-specific values are located in Controlling the maximum back-end sessions.

Feedback