PH65121: LDAP REGISTRY INITIALIZATION DELAY

APAR status

• Closed as program error.

Error description

• The delay during initialization occurs when the product queries
  LDAP to determine its schema and select the optimal group search
  method. This process involves extensive evaluation of user/group
  objects and can be time-consuming, depending on LDAP's
  complexity and network condition.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  *                  experiencing slow LDAP initialization       *
  *                  during                                      *
  *                  server startup                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: The server takes a long time to start   *
  *                      due                                     *
  *                      to slow LDAP initialization.            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  During server startup, LDAP initialization includes a one-time
  schema lookup to determine the best way to query users and
  groups.
  This process can be slow due to factors like LDAP configuration,
  network latency, new security settings, or complex user/group
  structures.
  

Problem conclusion

• With this APAR, the server will print the time (in milliseconds)
  taken for the schema check during LDAP initialization, along wit
  the query results in its trace.
  
  It will also provide information on how to preconfigure the quer
  result, allowing the server to use the saved result on the next
  startup and skip the schema check, significantly improving
  startup time.
  
  To see this information in the logs, enable the trace option:
  com.ibm.ws.security.registry.*=all
  
  The fix for this APAR is targeted for inclusion in fix pack
  8.5.5.28 and 9.0.5.24. For more information, see 'Recommended
  Updates for WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

Temporary fix

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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels