PM08217: VMM DIDN'T CACHE NULL-VALUED LDAP ATTRIBUTES IN THE CACHE, WHICH MAY BRING EXTRA LDAP CALLS EACH TIME THEY'RE REQUESTED

Fixes are available

APAR status

Closed as program error.

Error description

The null-valued Ldap attributes not in virtual member manager
(VMM) attributes cache caused extra Ldap calls. VMM has to
fetch them from Ldap in each get() API call although the value
is always null in the return attributes list. This may bring
extra Ldap communication.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server                                      *
****************************************************************
* PROBLEM DESCRIPTION: VMM didn't cache null-valued            *
*                      attributes in the attributes cache      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If an LDAP attribute has a null value, it isn't cached in the
VMM attributes cache because JNDI doesn't return the
null-valued attribute in get call. This caused an issue that
VMM didn't cache null-valued attribute in attributes cache,
then when getting this null-valued attribute with VMM again,
because no such attribute in the cache, VMM sets it in missing
attribute list and gets this null value again from LDAP. It
caused a performance issue for some customers who requested
such null-valued attributes for every application login,
because many useless Ldap calls introduced by such design

Problem conclusion

The problem has been fixed and the performance improved.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.33 and 7.0.0.11  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
PM08217
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-02-22
Closed date
2010-04-19
Last modified date
2011-08-03

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
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PM08217: VMM DIDN'T CACHE NULL-VALUED LDAP ATTRIBUTES IN THE CACHE, WHICH MAY BRING EXTRA LDAP CALLS EACH TIME THEY'RE REQUESTED

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

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?