Performance problem when using LDAPS
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
After setting an LDAP directory connector to use SSL (Secure Connection), the Crowd instance and/or integrated applications exhibit performance problems.
Cause
The default JNDI/LDAP service provider in Java does not pool SSL connections by default, which means every LDAP request must open a new connection to the server (reference).
Resolution
To force the JVM to pool SSL connections, add the following line to your Apache Tomcat /bin/setenv.sh (setenv.bat for Windows) file:
On Linux:
1
JAVA_OPTS="$JAVA_OPTS -Dcom.sun.jndi.ldap.connect.pool.protocol='plain ssl' -Dcom.sun.jndi.ldap.connect.pool.authentication='none simple DIGEST-MD5'"On Windows:
1
JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.jndi.ldap.connect.pool.protocol="plain ssl" -Dcom.sun.jndi.ldap.connect.pool.authentication="none simple DIGEST-MD5"If you wish to customize the SSL connection pooling further, please see the full documentation provided by Sun.
Was this helpful?