PM20517: AFTER 8 HOURS THREADS ARE HUNG ON VMM CODE

Fixes are available

APAR status

Closed as program error.

Error description

Description:

System configured to work with SSL against LDAP server.
WebSphere Application Server is configured to use zCrypto
hardware accelerator for SSL. After 8 hours the long run does
start getting Login errors which are caused by a hang on:


[8/9/10 1:21:12:988 EDT] 00000002 ThreadMonitor W   WSVR0605W:
Thread
"WebContainer : 21" (00000064) has been active for 646917
milliseconds
and may be hung.  There is/are 23 thread(s) in total in the
server that
may be hung.
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:196)
at
com.ibm.ws.wim.adapter.ldap.LdapConnection.getDirContext(LdapCon
nection.
java:1547)
at
com.ibm.ws.wim.adapter.ldap.LdapConnection.search(LdapConnection
.java:26
96)
at
com.ibm.ws.wim.adapter.ldap.LdapConnection.checkSearchCache(Ldap
Connecti
on.java:2664)
at
com.ibm.ws.wim.adapter.ldap.LdapConnection.search(LdapConnection
.java:28
54)
at
com.ibm.ws.wim.adapter.ldap.LdapConnection.searchEntities(LdapCo
nnection
.java:3059)
at
com.ibm.ws.wim.adapter.ldap.LdapAdapter.login(LdapAdapter.java:2
672)

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V6.1 and V7.0                        *
****************************************************************
* PROBLEM DESCRIPTION: In Virtual Member Manager threads are   *
*                      hung due to unavailability of context   *
*                      object.                                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
In Virtual Member Manager threads are hung after some time
(approx.8 hrs) due to unavailability of context object.

Problem conclusion

Updated the code to correct the logic for counting the live
context object available.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.35 and 7.0.0.13.  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
PM20517
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61Z
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-08-16
Closed date
2010-08-31
Last modified date
2011-06-18

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
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

PM20517: AFTER 8 HOURS THREADS ARE HUNG ON VMM CODE

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

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?