PM30134: STANDALONE LDAP CONFIGURATION FAILOVER IGNORES CONNECT TIMEOUT COM.SUN.JNDI.LDAP.CONNECT.TIMEOUT

Fixes are available

APAR status

Closed as program error.

Error description

If a standalone LDAP configuration has 4 servers listed with a
search timeout of 5 seconds (com.sun.jndi.ldap.connect.timeout).
When the 3rd server comes off the network ( valid DNS entry but
no reply from ping ) the WebSphere JVMs pause while starting for
about 3 minutes trying to connect to the "down" LDAP server.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server                                      *
****************************************************************
* PROBLEM DESCRIPTION: JVM startup is delayed by 3 min for     *
*                      each configured ssl-enabled LDAP        *
*                      server which is off the network.        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
On server startup, for each configured ssl-enabled LDAP
server which is down, a delay of 3 minutes per server is seen.

Problem conclusion

On server startup, a check is made to try to connect with each
configured LDAP server.  In the case of an ssl-enabled LDAP
server, a 3 min delay occurs.   There is currently no way for
a customer to specify a customizable maximum delay value in
order to minimize the overall delay in startup.

A custom property is introduced,
"com.ibm.websphere.security.ldapSSLConnectionTimeout", and is
configured as a custom property on the Global Security
settings.   It represents a delay in milliseconds, and must
have a value of > 0; a value of <=  0 results in the default
behavior.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.19.  Please refer to the Recommended
Updates
page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM30134
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-01-10
Closed date
2011-06-06
Last modified date
2011-06-06

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

R700 PSY
UP
R800 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 October 2021

Tips

PM30134: STANDALONE LDAP CONFIGURATION FAILOVER IGNORES CONNECT TIMEOUT COM.SUN.JNDI.LDAP.CONNECT.TIMEOUT

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY

R800 PSY

Document Information

Share your feedback

Need support?