PI81923: LDAPRegistry contextPool defaults do not match documentation

Fixes are available

APAR status

Closed as program error.

Error description

When a contextPool for an LDAPRegistry is not specifically
configured, the defaults for the maxSize and preferredSize
do not match the defaults documented in the Knowledge
Center. For example, when the contextPool is not customized,
the default maxSize is set to 1 which could result in slow
LDAP connections or logins appearing to hang.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of IBM WebSphere Application Server   *
*                  Liberty using the LDAPRegistry and have not *
*                  configured a contextPool                    *
****************************************************************
* PROBLEM DESCRIPTION: LDAPRegistry contextPool defaults do    *
*                      not match documentation                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When a contextPool for an LDAPRegistry is not specifically
configured, the defaults for the maxSize and preferredSize do
not match the defaults documented in the Knowledge Center. For
example, when the contextPool is not configured, the default
maxSize is set to 1 which could result in slow LDAP connections
or logins appearing to hang.

Problem conclusion

The default for maxSize was set to the documented default of 0.
The default for preferredSize were set to the documented default
of 3.

To workaround this problem, configure a contextPool for your
LDAPRegistry and set the maxSize and preferredSize.

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

Temporary fix

To workaround this problem, configure a contextPool for your
LDAPRegistry and set the maxSize and preferredSize.

Comments

APAR Information

APAR number
PI81923
Reported component name
WAS LIBERTY COR
Reported component ID
5725L2900
Reported release
CD0
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-05-19
Closed date
2017-07-04
Last modified date
2017-07-04

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
WAS LIBERTY COR
Fixed component ID
5725L2900

Applicable component levels

RCD0 PSY
UP

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

Document Information

Modified date:
04 May 2022

Tips

PI81923: LDAPRegistry contextPool defaults do not match documentation

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

RCD0 PSY

Document Information

Share your feedback

Need support?