OID 11g Outage / Slow Down LIBOVD-40066 LDAP response read timed out / DIP-10512 Error in making a remote call to provisioning bean
(Doc ID 2125137.1)
Last updated on SEPTEMBER 11, 2023
Applies to:
Oracle Internet Directory - Version 11.1.1.7.0 and laterInformation in this document applies to any platform.
Symptoms
On : 11.1.1.7.0 version, Directory Integration Platform
Production outage/slow down
Not able to get a connection to the production. Getting timeout errors.
ERROR
-----------------------
OAM logs show:
[2016-03-30T08:42:35.384-07:00] [oam_server1] [WARNING] [LIBOVD-40066] [oracle.ods.virtualization.engine.backend.jndi.ids_asp] [tid: [ACTIVE].ExecuteThread: '124' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: ] [ecid: <ECID>] [APP: oam_server#11.1.2.0.0] [URI: /oam/server/auth_cred_submit] Remote Server Failure:<OID_HOSTNAME>:<OID_PORT>.[[
javax.naming.NamingException: LDAP response read timed out, timeout used:150000ms.; remaining name 'cn=Users,dc=<COMPANY>'
at com.sun.jndi.ldap.Connection.readReply(Connection.java:483)
[2016-03-31T08:51:45.383-07:00] [wls_ods1] [TRACE] [DIP-10002] [oracle.dip.<SYNC_PROFILE_NAME>] [tid: <SYNC_PROFILE_NAME>] [userId: ] [ecid: <ECID>] [APP: DIP#11.1.1.2.0] [SRC_CLASS: oracle.ldap.odip.web.DIPSyncBean] [SRC_METHOD: mapEnd] ending mapping execution
[2016-03-31T08:52:38.289-07:00] [wls_ods1] [ERROR] [DIP-10512] [oracle.dip.syndication.<PROV_PROFILE_NAME>] [tid: <PROV_PROFILE_NAME>E] [userId: ] [ecid: <ECID>] [APP: DIP#11.1.1.2.0] Error in making a remote call to provisioning bean : {0}[[
[2016-03-31T08:52:41.164-07:00] [wls_ods1] [NOTIFICATION] [DIP-10580] [oracle.dip] [tid: UpdateThread] [userId: ] [ecid: <ECID>] [APP: DIP#11.1.1.2.0] changelog filter : (&(changenumber>=18446414)(|(targetdn=*cn=Profiles,cn=Provisioning,cn=Directory Integration Platform,cn=Products,cn=OracleContext)(targetdn=*cn=event definitions,cn=directory integration platform,cn=products,cn=oraclecontext)(targetdn=*cn=object definitions,cn=dir
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Perform DIP sync
2. Encounter slowness
3. Error shows in logs.
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |