PM94008: Timed-out ldap bind and search failures on reused connections are not retried.

Fixes are available

APAR status

Closed as program error.

Error description

LDAP access can intermittently take a long time or timeout
because retries are not being performed for bind and search
failures as with other ldap failures.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  IBM HTTP Server users that are also using   *
*                  LDAP                                        *
****************************************************************
* PROBLEM DESCRIPTION: Retries are not being attempted for     *
*                      ldap search failures or bind timeouts.  *
****************************************************************
* RECOMMENDATION:  Apply this fix if using LDAP with IHS.      *
****************************************************************
Retries were not being performed for bind and search failures
as with other ldap failures.  For some configurations, this
was resulting in ldap access either taking a long time and/or
timing out.

Problem conclusion

Retries are now performed for ldap bind and search failures.
A new 'LDAPRetries' directive has also been added for
specifying the number of retries to be performed (default of
'3' on Windows and '4' on non-Windows platforms).  It can be
set using the syntax of:
 LDAPRetries 4
A bind timeout (in seconds) can be specified using the
LDAPBindTimeout directive introduced with APAR PM45618. Though
the default value is '0' (unlimited), it is suggested that
this be set to approximately '5' seconds.

This fix is targeted for IBM HTTP Server fix packs:
- 7.0.0.31
- 8.0.0.8
- 8.5.5.2

Temporary fix

Comments

APAR Information

APAR number
PM94008
Reported component name
IBM HTTP SERVER
Reported component ID
5724J0801
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-07-29
Closed date
2013-10-29
Last modified date
2013-10-29

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
IBM HTTP SERVER
Fixed component ID
5724J0801

Applicable component levels

R700 PSY
UP
R800 PSY
UP
R850 PSY
UP

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

Document Information

Modified date:
07 September 2022

Tips

PM94008: Timed-out ldap bind and search failures on reused connections are not retried.

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

R850 PSY

Document Information

Share your feedback

Need support?