PI86719: The LDAPRegistry contextPool timeout setting does not timeout after the configured time

Fixes are available

APAR status

Closed as program error.

Error description

The LDAPRegistry contextPool timeout setting does not
timeout at the expected interval.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server Liberty- Virtual Member Manager      *
*                  (VMM) with the LDAPRegistry contextPool     *
*                  enabled with a custom timeout configured.   *
****************************************************************
* PROBLEM DESCRIPTION: ContextPool does not timeout at the     *
*                      expected interval                       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The LDAPRegistry contextPool timeout setting does not timeout at
the configured time. The timeout will occur later than
configured. If the context pool is configured to timeout before
another application breaks connections, the connection may not
timeout after the expected timeout.

Problem conclusion

The LDAPRegistry contextPool timeout setting was corrected to
timeout at the configured time.

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

Comments

APAR Information

APAR number
PI86719
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-08-31
Closed date
2017-09-14
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
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

PI86719: The LDAPRegistry contextPool timeout setting does not timeout after the configured time

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?