WebLogic Uses Too Many Embedded LDAP "LDAPCONNTHREAD-#" Threads and LDAPS Connections
(Doc ID 2390101.1)
Last updated on SEPTEMBER 07, 2021
Applies to:Oracle WebLogic Server - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 12c]
Information in this document applies to any platform.
After upgrading a Weblogic domain, the number of LDAP connections between managed servers and the admin server grew in comparison to previous releases. In previous WebLogic versions, six LDAP connection threads were common. The number of LDAP connections varied from 2 to over 40 connections. As soon as a managed server started up, embedded LDAP connections appeared. The number was unpredictable, but the number of LDAP connections for a particular managed server was consistent between server restarts.
To test if a managed server is exhibiting this problem, start the managed server with WebLogic property -Dweblogic.security.ldap.poolsize=x on the Java startup command line, where "x" is the number of threads in the LDAP pool. For this particular test, set "x" equal to 2 threads (i.e. -Dweblogic.security.ldap.poolsize=2). Start the server, and then capture three thread dumps 15 seconds apart. For instructions on how to capture a thread dump, refer to "Different ways to take thread dumps in WebLogic Server (Doc ID 1098691.1)" on My Oracle Support.
Next, look at the thread dumps. When the managed server is running, the thread stacks for the LDAP connection threads will appear as below. If you count more than "x=2" LDAPConnThreads, then you have hit this problem.
The behavior was observed after upgrading WebLogic Server from version 18.104.22.168.0 to 22.214.171.124.0.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document