LDAP: error code 53 - DB locks threshold is reached (nsslapd-db-locks-monitoring-threshold) in RHSSO

Solution Unverified - Updated -

Issue

Some custom plugins integrated in RHSSO execute multiples queries to LDAP server reaching a maximum number set up in the LDAP server parameter named nsslapd-db-locks-monitoring-threshold

ERROR [org.keycloak.storage.ldap.idm.store.ldap.LDAPOperationManager] (default task-13342) Could not query server using DN [cn=users,cn=accounts,dc=organization,dc=org] and filter [(&(uid=user)(objectclass=top)(objectclass=inetOrgPerson)(objectclass=organizationalPerson)(objectclass=person)(objectclass=nsMemberof)(objectclass=customers))]: javax.naming.OperationNotSupportedException: [LDAP: error code 53 - DB locks threshold is reached (nsslapd-db-locks-monitoring-threshold)]; remaining name 'cn=users,cn=accounts,dc=organization,dc=org'
    at java.naming/com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3332)
    at java.naming/com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3205)
    at java.naming/com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2996)
    at java.naming/com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1875)
    at java.naming/com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1798)
    at java.naming/com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirContext.java:392)
    at java.naming/com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:358)

Environment

  • RHSSO 7.6.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content