Connection Pooling

Connections are used for multiple client requests and CipherTrust Manager responses. Once opened, connections are cached in a connection pool. You set the properties that determine the maximum size of the connection pool, and control how long unused connections are maintained.

How it Works

The following steps describe what happens when connection pooling is enabled and the client attempts to connect to the server:

1. The application calls for a connection to the CipherTrust Manager.

2. The client checks that Use_Persistent_Connections is set to yes.

3. The client searches the connection pool for an existing connection.

4. The client uses an existing connection if one is available. Otherwise, it creates a new connection if there is a space in the pool. If space is not available, the client returns an error.

5. The client uses the connection to communicate with the server.

6. When the operation is complete, the connection stays in the pool and can be reused by the client. The connection pool will close any connections that have been idle for the length of the Connection_Idle_Timeout.

No more than 300 connections can exist at one time. The size of the pool actually starts at 0 and can scale to 300 as needed. Unused connections are closed according to the Connection_Idle_Timeout, and the connection pool shrinks when fewer connections are needed. If a connection is not being used, it will be closed after 10 minutes.

Related Properties

To use connection pooling, you need to set the following parameters in the properties file:

• Use_Persistent_Connections

• Size_of_Connection_Pool

• Connection_Idle_Timeout

Refer to Connection Configuration Parameters to know more about the connection configuration related properties.