Configuring the LDAP connection pool

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. 

The default implementation for LDAP connection pooling is using JNDI and the pool settings are set via system properties when starting Crowd.

Use system properties instead of updating the settings in Crowd

Because of a bug, the ‘Update Settings’ form used to specify the LDAP connection pool properties directly in Crowd won’t work. Any values that you set will not have any effect. Use this page to configure the connection pool using system properties instead.

View the current configuration

You can view the current settings for LDAP connection pooling in Crowd.

To view the current configuration:

  1. Log in to the Crowd Administration Console.

  2. In the top navigation bar, select Administration.

  3. In the left-hand menu, select LDAP Connection Pool.

Configure the LDAP connection pool

To configure the JNDI connection pool:

  1. Go to <installation-directory>/bin, and edit the (Linux) or setenv.bat (Windows) file.

  2. Set the properties from the table below, for example: 


Pool properties


Crowd system property


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 0 (zero) means that there is no preferred size, so the number of idle connections is unlimited.


Maximum pool size


The max 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 0 (zero) means that the number of connections is unlimited.


Pool timeout


The length of time, in milliseconds, 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 0 (zero) means that the idle time is unlimited, so connections will never be timed out.


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:

  • plain
  • ssl

plain ssl 
(Both plain and ssl)

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:

  • none
  • simple


Last modified on Jun 28, 2022

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.