Using Oracle Virtual Directory (OVD) with WebLogic Server (WLS) Authentication Can Be Very Slow And Relevant Threads Get Stuck (Doc ID 1313207.1)

Last updated on MAY 24, 2017

Applies to:

Oracle Weblogic Server - Version: 10.3 and later   [Release: and later ]
Information in this document applies to any platform.

Goal


Using Oracle Virtual Directory (OVD) Security Provider with WLS 10.3 and SOA / BPM, the 2nd step of the Login process can be very slow for no apparent reason.  Thus, threads get stuck and users get prevented from sucessful login.

The thread dumps clearly indicate of possible delay in obtaining information from the LDAP as the threads are getting stuck (see example below) while communicating with the LDAP server.

"[STUCK] ExecuteThread: '14' for queue: 'weblogic.kernel.Default (self-tuning)'" id=318 idx=0x2a0 tid=23416 prio=1 alive, waiting, native_blocked, daemon
-- Waiting for notification on: netscape/ldap/LDAPResponseListener@0xfee7fea0[fat lock]


Solution

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