Connection pooling improves the performance of requests to the LDAP directory servers. It is a technique used for sharing server resources among requesting clients. Without connection pooling, each request to the LDAP directories causes a new connection to the directory server to be created and then released when the connection is no longer required. The overhead in creating and releasing these connections has adverse effects on performance. With connection pooling, connections are stored in pools after they have been established and are reused for subsequent requests.
A connection can have the following states:
· open: either in use or idle
· in use: open connection currently in use
· idle: open connection available for reuse
· closed: no longer available for use
The following diagram illustrates which actions are possible on connections:
The properties are divided into the following groups:
● Connection pooling properties of the user management engine (UME)
● Connection pooling properties of the data source configuration file
For information about other LDAP properties, see LDAP Directory Data Source.
Connection Pooling Properties of the UME
Property |
Value |
Description |
ume.ldap.connection_pool. |
Default value is 5. |
Maximum number of idle connections in the connection pool. If the maximum number of idle connections is reached, the connection pool closes every incoming released connection. |
ume.ldap.connection_pool. |
Default value is 300,000. |
Maximum time in milliseconds for an idle connection in the connection pool. |
ume.ldap.connection_pool. |
Default value is 10. |
Maximum number of connections in the connection pool. |
ume.ldap.connection_pool. |
Default value is 60,000. |
Maximum time in milliseconds that a process waits if no connection is available. |
ume.ldap.connection_pool. |
Default value is 1. |
Minimum number of connections in the connection pool. For example, if this value is set to ‘1’, the connection pool never has less than 1 open connection. |
ume.ldap.connection_pool. |
Default value is 0 (logging is disabled). |
Interval in milliseconds at which monitoring information is written. Any value less than 1000 disables logging. For more information, see Directory Server Connection Pool Log. |
ume.ldap.connection_pool. |
Default value is 2. |
Number of attempts to open a connection if a connection fails. If all attempts fail, an error message is written the security log the default trace file. If high availability is enabled, the UME switches to the next directory server. See also Logging and Tracing. |
ume.ldap.connection_pool. |
Default value is 10,000. |
Interval in milliseconds before retrying to open a connection. |
The following properties only appear in the private section of the data source configuration file. For more information about the private section, see <privateSection>.
Connection Pooling Properties of the Data Source Configuration File
Property |
Value |
Description |
ume.ldap.connection_pool. |
Default value is 0. 0 = No limit. |
Defines the maximum lifetime of a connection in the connection pool. Use this setting if your firewall automatically blocks connections after a set period of time. This enable the UME to proactively close connections and negotiate new ones without waiting for old connections to time out. |
ume.ldap.connection_pool. |
Default value is 25000. |
Defines the amount
of time in milliseconds between connection requests sent from the UME to the directory server. The UME
retries the connection the number of times specified in ume.ldap.connection_pool. See also SAP Note 829965. |