TOO MANY EMBEDDED LDAP "LDAPCONNTHREAD-#" THREADS AND LDAPS CONNECTIONS

(Doc ID 2390101.1)

Last updated on APRIL 24, 2018

Applies to:

Oracle WebLogic Server - Version 12.2.1.2.0 and later
Information in this document applies to any platform.

Symptoms

After upgrading a Weblogic domain, the numbers 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. When the managed servers started, the thread stacks for the LDAP connection threads appeared as below.

  "LDAPConnThread-0 ldaps://localhost:8001" #57 daemon prio=5 os_prio=0
tid=0x0000000064a1e800 nid=0x3420 runnable [0x000000006a67e000]
  java.lang.Thread.State: RUNNABLE
  at java.net.SocketInputStream.socketRead0(Native Method)
  at
java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
  at java.net.SocketInputStream.read(SocketInputStream.java:171)
  at java.net.SocketInputStream.read(SocketInputStream.java:141)
  at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
  at java.io.BufferedInputStream.read(BufferedInputStream.java:265)
  - locked (a java.io.BufferedInputStream)
  at netscape.ldap.ber.stream.BERElement.getElement(Unknown Source)
  at netscape.ldap.LDAPConnThread.run(Unknown Source)
  at java.lang.Thread.run(Thread.java:748)

Changes

 The behavior was observed after upgrading WebLogic Server. 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms