
Documentation for Crowd 2.1.x. Documentation for other versions of Crowd is available too.
This page contains an overview of the new connection pool for LDAP directories in Crowd 2.1 Beta 2.
When connection pooling is enabled, the LDAP service provider maintains a pool of connections and assigns them as needed. When a connection is closed, LDAP returns the connection to the pool for future use. This can improve performance significantly.
This page describes the site-wide settings for LDAP connection pooling in Crowd.
To configure the LDAP connection pooling in Crowd,
Connection Pool Setting |
Description |
Default Value |
|---|---|---|
Initial Pool Size |
The number of LDAP connections created when initially connecting to the pool. |
|
Preferred Pool Size |
The optimal pool size. LDAP will remove idle connections when the number of connections grows larger than this value. A value of |
|
Maximum Pool Size |
The maximum number of connections. When the number of connections reaches this value, LDAP will refuse further connections. As a result, requests made by an application to the LDAP server will be blocked. A value of |
|
Pool Timeout |
The length of time, in seconds, that a connection may remain idle before being removed from the pool. When the application is finished with a pooled connection, the connection is marked as idle, waiting to be reused. A value of |
|
Pool Protocol |
Only these protocol types are allowed to connect to LDAP. If you want to allow multiple protocols, enter the values separated by a space. Valid values are:
|
|
Pool Authentication |
Only these authentication types are allowed to connect to LDAP. If you want to allow multiple authentication types, enter the values separated by a space. See RFC 2829 for details of LDAP authentication methods. Valid values are:
|
|
Screenshot: LDAP Connection Pool