JR52746: INCONSISTENT SEARCH RESULTS FOR TASKS ASSIGNED TO USERS THAT ARE NOT IN THE USER REPOSITORY

8.0.1.2-WS-BPM-IFJR52746
8.0.1.3-WS-BPM-IFJR52746
8.5.5.0-WS-BPM-IFJR52746
8.5.6.0-WS-BPM-IFJR52746
8.5.0.1-WS-BPM-IFJR52746
bpm.8560.cf1.delta.repository.1
bpm.8560.cf1.delta.repository.2
Version 8.5.0 Fix Pack 2 for the IBM Business Process Manager products
Version 8.5 Refresh Pack 7 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• When a user who has tasks assigned to him or her in IBM Business
  Process Manager (BPM) is deleted from the user registry, the
  results of some API calls can become inconsistent regarding that
  user. For example, using the Search REST API to query tasks that
  are assigned to that user might or might not return results,
  depending on the current state of the application.
  
  
  During application deployment the time to finish installing the
  snapshot takes a very long time, possibly one (1) hour. This
  could also impact instance migration during the team migration
  part.  During these actions, calls to UserOrgModule.userExists,
  UserInfoCache.loadCacheData, UserCore.getOrCreateUserInfoObject
  will show up in trace for every user associated with the
  application. You may also see calls for other group caches being
  reloaded.
  

Local fix

Problem summary

• IBM BPM synchronizes user information from the WebSphere
  Application Server user registry. When a user is deleted from
  the user registry, the deletion is not propagated to IBM BPM
  because the user might still have tasks assigned to him or her.
  So, although the user is no longer able to log in to the system,
  the user record continues to be available when another user logs
  in and refers to the deleted user.
  Either the user's name or the user's ID in the database is used
  to look up a user. If the user's name is used, a check is
  performed to determine whether the user exists in the WebSphere
  Application Server user registry. If the user's ID is used, no
  such check is performed. As a result, an inconsistency occurs
  regarding user look ups. In particular, calling the Search REST
  API to query tasks by user name produces diverging results,
  depending on whether a lookup by user ID took place before the
  API call.
  A secondary problem resolved with APAR is a performance issue
  with application deployments. The performance issue increases
  with the size of the LDAP and the size of groups associated
  with the app. During application deployment user and group
  registries (local and LDAP) for the members  associated with
  the app will be checked. It will do this for every memer and
  group.  Calls such as UserOrgModule.userExists,
  UserInfoCache.loadCacheData, UserCore.getOrCreateUserInfoObject
  will appear in a WLE.*=all search during application deployment.
  After installing this fix the time to install a new snapshot
  decreases dramatically.
  

Problem conclusion

• A fix is/will be available for IBM BPM that changes the user
  cache implementation by modifying the current lookup behavior
  for user names so that the check to determine the user's
  existence in the WebSphere Application Server user registry is
  no longer performed. Unlike before the fix is applied, both
  lookup types now lead to the same result by disregarding user
  existence in the WebSphere Application Server user registry.
  On Fix Central (http://www.ibm.com/support/fixcentral), search
  for JR52746:
  1. Select IBM Business Process Manager with your edition from
    the product selector, the installed version to the fix pack
    level, and your platform, and then click Continue.
  2. Select APAR or SPR, enter JR52746, and click Continue.
  When you download fix packages, ensure that you also download
  the readme file for each fix. Review each readme file for
  additional installation instructions and information about the
  fix.
  

Temporary fix

• Not applicable
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  BPM STANDARD

• Fixed component ID

  5725C9500

Applicable component levels