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 AUGUST 31, 2020
Applies to:Oracle WebLogic Server - Version 10.3 and later
Information in this document applies to any platform.
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 successful 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=<tid> prio=1 alive, waiting, native_blocked, daemon
-- Waiting for notification on: netscape/ldap/LDAPResponseListener@0xfee7fea0[fat lock]
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