Connection Pooling

Persistent connections are connections that are used for multiple client requests and NAE Server responses.

Connections in the pool can be active or waiting, TCP or SSL. A connection is created as needed, and the pool scales as needed. The pool starts at size 0, and can grow to Size_of_Connection_Pool. Once the pool is full, new connection requests must wait for an existing connection to close. Connection pooling is configured for a client session on per server basis. The size of the pool applies to each client-session for a server, it is not a total value for a Key Manager or for a load balancing group. Regardless of your setting, the pool will always have at least 2 connections per NAE Server. The larger your connection pool, the less likely your client will get a failed connection request.

How it works

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

1. Your application calls for a connection to the Key Manager.

2. The client checks whether the Use_Persistent_Connections is set to yes.

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

4. If connection is available, the client uses an existing connection. Else, it creates a new connection if there is space in the pool.

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.

Related parameters

• Use_Persistent_Connections

• Size_of_Connection_Pool

• Connection_Idle_Timeout

For more information about these parameters, refer to Connection Parameters.