OIM Going into Warning State and WebLogic Console Showing Stuck Threads [waiting on (a com.sun.jndi.ldap.LdapRequest)]
(Doc ID 1923106.1)
Last updated on FEBRUARY 25, 2019
Applies to:Identity Manager - Version 184.108.40.206.0 and later
Oracle Internet Directory - Version 10.1.4 to 11.1.1 [Release 10gR3 to 11g]
Information in this document applies to any platform.
Oracle Identity Manager (OIM) 11g integrated with Oracle Internet Directory (OID) 10g or 11g. No OIM ldap sync and no libovd are involved, only a custom OIM LDAP connector for OID is being used.
OIM going into warning state and Weblogic console is showing stuck threads.
Depending on what server in OIM weblogic cluster is running jobs, seeing different 'STUCK' messages in the oim_server diagnostic logs along with the health of the OIM servers going into a 'Warning' state in the Weblogic console. These stuck threads are causing downstream effects on the jobs running.
OIM log does not show many threads for OIM, however it shows almost 2000 LDAPConnectionThread's, for example:
NOTE: In the log snippet above the ldap details represent a fictitious sample. Any similarity to actual environments, is purely coincidental and not intended in any manner.
No OID log errors can be found that correspond to date/time of failures, and no high OID operation times (OPtime) values in debugged OID logs either.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!