APAR status
Closed as program error.
Error description
When a WebSphere Application Server does lookups into LDAP, it
is making more LDAP calls than necessary. Can the calls be
streamlined to improve performance?
Local fix
No workaround exists for this issue.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server who have *
* enabled security and are using LDAP as the *
* configured user registry. *
****************************************************************
* PROBLEM DESCRIPTION: An unnecessary JNDI lookup() operation *
* was performed for each search *
* operation. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An unnecessary JNDI lookup() operation was performed for each
search operation. This call was made to instantiate a
directory context.
Problem conclusion
A directory context pool was implemented and a new directory
context is now only instantiated in the case where an existing
context is not available for use gretly reducing the number
of LDAP calls used to instantiate directory contexts.
This is for performance reasons only. There was no functional
loss associated with this issue.
Temporary fix
Fix test provided.
Comments
APAR information |
APAR number |
PQ81024 |
Reported component name |
WEBSPHERE AE AI |
Reported component ID |
5630A2200 |
Reported release |
400 |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Submitted date |
2003-11-17 |
Closed date |
2003-12-18 |
Last modified date |
2003-12-18 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
SRLS
Applicable component levels |
R400 PSY |
UP |
|