-
Bug
-
Resolution: Fixed
-
Highest
-
None
-
18
-
Severity 2 - Major
-
37
-
The LDAP pool configuration set in the UI doesn't have any effect. It's set too late in the startup process, so the defaults have already been set.
CWD-4070 showed the real values and set them with a system property in Tomcat's configuration. This will need to be taken further, improving the presentation of the current settings and making it easier to set new values.
Or, given the complexity, implement CWD-2790 instead.
- causes
-
JRASERVER-62728 Regression - Pool SSL LDAP connections
- Gathering Impact
-
CONFSERVER-79770 Confluence does not explicitly specify LDAP protocols for pooling
- Closed
- is duplicated by
-
CWD-4635 LDAP connection pool settings are not being respected
- Closed
- is related to
-
BSERV-8586 Bitbucket Server using ldaps makes clone perform slower than using ldap
- Closed
-
CWD-2790 Use Spring LDAP's connection pooling support
- Closed
-
CWD-4012 Harmonise and clarify JNDI connection pooling
- Closed
-
CWD-4070 Pool SSL LDAP connections
- Closed
- relates to
-
FE-6467 Verify we enable SSL connection pooling for LDAP servers
- Closed
-
KRAK-4939 Loading...
-
KRAK-4951 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
- was cloned as
-
KRAK-2631 Loading...