Failed Network Connections on Managed Server Caused NMS Clients to Hang "Waiting for LDAP"
(Doc ID 2714159.1)
Last updated on NOVEMBER 28, 2023
Applies to:
Oracle Utilities Network Management System - Version 2.3.0.2.0 and laterOracle Network Management for Utilities - DMS - Version 2.3.0.2.0 and later
Information in this document applies to any platform.
Symptoms
On : 2.3.0.2.0 version, Web Workspace
Several different groups of users had their Web Workspace environments lock up.
Not all users were affected.
After rebooting their desktops, the affected operators were able to log back in to Web Workspace and resume their normal operations.
The diagnostic image from the NMS managed server had a number of waiting LDAP threads:
Thread 305: Waiting for LDAP
Thread 301: Waiting for CORBA acknowledgeEvents()
Thread 261: In the middle of a LDAP request
Thread 267: Waiting for CORBA getIncidents()
Thread 250: Waiting for LDAP
Thread 248: Transferring data to client
Thread 228: Transferring data to client
Thread 177: Waiting for LDAP
Thread 163: Waiting for LDAP
Thread 139: Waiting for LDAP
Thread 141: Waiting for LDAP
Thread 133: Waiting for LDAP
Thread 103: Waiting for LDAP
Thread 98: Updating a damage assessment using JDBC
Thread 93: Waiting for LDAP
Thread 88: Waiting for LDAP
Thread 86: Waiting for LDAP
Thread 78: Waiting for LDAP
Thread 70: Waiting for LDAP
Thread 67: Waiting for CORBA unassoiciateEvent()
Thread 74: Processing a dumpCacheSummary() request
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 |
| Managed Server Specific Changes |
| LDAP Provider Setting Changes |
| References |