PH44422: LDAP CONNECTION RETRIES TAKE LONG TIME

APAR status

• Closed as program error.

Error description

• In standalone LDAP configuration,
  com.sun.jndi.ldap.connect.timeout property gets unset due to
  a bug. As a result, users would need to wait for a long time
  to find out when the LDAP is unavailable.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  *                  who is using Standalone LDAP or Federated   *
  *                  repositories for a zOS RACF LDAP            *
  ****************************************************************
  * PROBLEM DESCRIPTION: When LDAP is unavailable, users had to  *
  *                      wait for a long time until the LDAP     *
  *                      search timeout happens.                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  In standalone LDAP configuration and federated repository
  configuration for a RACF LDAP, there were scenarios when
  com.sun.jndi.ldap.connect.timeout property
  was unset due to a bug.
  As a result, users would need to wait for a long time to find
  out
  when the LDAP is unavailable.
  

Problem conclusion

• The bug has been fixed. The default timeout is set to 20 seconds
  
  The fix for this APAR is targeted for inclusion in fix pack
  8.5.5.23 and 9.0.5.14. 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