-
Suggestion
-
Resolution: Fixed
-
None
LDAP connections over SSL are not pooled, meaning each operation acquires a new TCP connection as well as negotiating SSL. This significantly increases the time taken for operations like synchronisation.
For a default Crowd with no pooling configuration changes, synchronisation is single threaded, so only a single connection is made. (In testing, two connections; it's not clear if that's due to multiple threads or a single connection only being reused so many times.)
In terms of impact, a synchronisation with OpenLDAP that took 1m45 without SSL took as much as 8m15 when SSL was enabled.
Fixing this may require CWD-2790.
- is related to
-
BSERV-8586 Bitbucket Server using ldaps makes clone perform slower than using ldap
- Closed
-
CWD-4012 Harmonise and clarify JNDI connection pooling
- Closed
- relates to
-
CWD-4159 LDAP pool configuration doesn't take effect
- Closed
-
FE-6467 Verify we enable SSL connection pooling for LDAP servers
- Closed
-
KRAK-260 Loading...
- was cloned as
-
CONFSERVER-35735 Pool SSL LDAP connections
- Closed
-
JRACLOUD-41025 Pool SSL LDAP connections
- Closed
-
JRASERVER-41025 Pool SSL LDAP connections
- Closed