PM95697: LDAP contexts getting leaked after first connection exception

Fixes are available

APAR status

Closed as program error.

Error description

LDAP contexts were getting leaked after first connection
exception.

Once VMM gets connection exception from LDAP server ,it again
tries to connect to LDAP and get a context with new context pool
creation with existing no.of contexts. But the issue is ,it was
creating context pool everytime and was not using existing
contexts available in pool.So everytime it gets Connection
excepion everytime VMM creates Context pool.

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server                                      *
****************************************************************
* PROBLEM DESCRIPTION: Redundant context pool creation once    *
*                      VMM gets a connection exception from    *
*                      an LDAP server                          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Once VMM gets a connection exception from an LDAP server, it
again tries to connect to LDAP, recreating the directory
context and gets a context with a new context pool creation
with the existing number of contexts. But the issue is, it was
creating a context pool every time and was not using existing
contexts available in the pool.

Problem conclusion

This fix corrects the code to propertly handle the context pool
when a connection failure occurs from the LDAP server.

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.45, 8.0.0.9 and 8.5.5.2 and fix pack 17.0.0.3
for WebSphere Application Server Liberty.  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
PM95697
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-08-23
Closed date
2017-06-05
Last modified date
2017-09-14

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
R850 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":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2022

Tips

PM95697: LDAP contexts getting leaked after first connection exception

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?