My Oracle Support Banner

Participant Search Using DirHumanParticipant.fetchMatchingName takes a Long Time (Doc ID 1209113.1)

Last updated on JANUARY 30, 2022

Applies to:

Oracle Business Process Management Suite - Version 10.3.1 and later
Information in this document applies to any platform.

Symptoms

DirHumanParticipant.fetchMatchingName is firing lot of queries to WCI LDAP as follows and takes more than 1 min to return results.

hybrid ldap search: dn[uid=test.1012211089,ou=ext,ou=users] filter[(&(objectclass=portalUserClass) (cn=*OFEI*))] attributes[[uniqueidentifier, phone, cn, givenName, sn, email, phone, uniqueidentifier, manager]] time[6 ms] Context[{jdbc.pool.idle_timeout=5, java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory, java.naming.referral=follow, jdbc.pool.entry.max=10, ldap.directory.property=<ALUI_HOME>/obpm10/conf/generic_aluidirectory.conf, java.naming.security.principal=uid=administrator,ou=users,dc=bea,dc=com, custom.fuego.directory.hybrid.ldap.manageOU=true, java.naming.ldap.version=3, custom.fuego.directory.hybrid.ldap.masterGroupDn=cn=OBPM-Master-Group,ou=groups,dc=bea,dc=com, jdbc.pool.min=0, custom.com.sun.jndi.ldap.connect.pool=true, java.naming.provider.url=ldap://<server>:<port>/dc=bea,dc=com, jdbc.pool.max=10, java.naming.security.credentials=<credentials>}] Trace: at fuego.directory.hybrid.ldap.JNDIQueryExecutor.logQuery(JNDIQueryExecutor.java:249)

Changes

Migrated environment from BPM 6.0.x with ALUI  to BPM 10.3.1 with WCI.

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
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.