Unable to Reassign an Instance because the Participant Search is not Responding (Doc ID 1115917.1)

Last updated on NOVEMBER 21, 2013

Applies to:

Oracle Business Process Management Suite - Version 5.7.3 to 10.3.1
Information in this document applies to any platform.
***Checked for relevance on 14-May-2012***

Symptoms

The installation is using Hybrid authentication based on MS Active Directory (MSAD) or other LDAP server.
A very specific reassign search (for a participant) works fine, but when the search is broad the search never returns (or it takes a very long time).

In other words, the participant search functionality is not responding in an acceptable amount of time. Searches for * are taking approximately 21 minutes to complete. You might see the following exception in the workspace.log:

<D>, "Aug 16, 2010 3:23:28 AM", Default, Main, <8> [STUCK] ExecuteThread, "The Maximum number of participants '500' to be returned was exceeded.
Caused by: The Maximum number of participants '500' to be returned was exceeded.
fuego.web.exception.WapiOperationException: The Maximum number of participants '500' to be returned was exceeded.
at fuego.workspace.model.common.PapiBean.getParticipantsFor(PapiBean.java:3004)
at fuego.workspace.model.common.PapiBean.getReassignParticipants(PapiBean.java:2333)
at fuego.workspace.model.view.AssignmentOperations$1.getParticipants(AssignmentOperations.java:35)
at fuego.workspace.model.view.AssignDialogBean.searchParticipant(AssignDialogBean.java:164)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms