OUD - Berkeley Database (BDB) Lock Causing High Etimes For LDAP Requests
(Doc ID 3012934.1)
Last updated on APRIL 05, 2024
Applies to:
Oracle Unified Directory - Version 12.2.1.4.221009 and laterInformation in this document applies to any platform.
Symptoms
OUD 12.2.1.4.221009 - BDB Java Edition Backend (BDB)
Multiple incidents were identified where applications were experiencing high etimes for ~10 minutes for ldap requests. Although the transactions had high etimes, they completed successfully.
When reviewing the logs for the transactions the following error example was observed:
[15/Sep/2023:12:31:32 -0400] category=JEB severity=SEVERE_ERROR msgID=8651009 msg=Error '(JE 7.0.7) Transaction 1620657445 must be aborted, caused by: com.sleepycat.je.LockTimeoutException: (JE 7.0.7) Lock expired. Locker 313368688 -1_Tombstones Purger Thread (cn=Common_name)_ReadCommittedLocker: waited for lock on database=cn_xxxx_objectClass.presence LockAddr:139158596 LSN=0x72d93/0x5451ea2 type=READ grant=WAIT_NEW timeoutMillis=600000 startTime=1694794892575 endTime=1694795492575
This error was found across other environments as well, sometimes locking other suffix as well. What is causing this lock and why?
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 |