IBM Support

PI20776: WSVR0605W HUNG THREAD IN UNAVAILABLEMANAGERIMPL

Fixes are available

8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • A hung thread message similar to the following will be
    generated in the SystemOut.log file...
    
    [5/14/14 15:38:44:498 CEST] 00000902 ThreadMonitor W
    WSVR0605W: Thread "WebContainer : 60" (00000430) has been
    active for 744963 milliseconds and may be hung.  There is/are 3
    thread(s) in total in the server that may be hung.
    at java.util.HashMap.put(HashMap.java:374)
    at
    com.ibm.ws.cluster.router.selection.UnavailableManagerImpl.markU
    navailable(UnavailableManagerImpl.java:279)
    at
    com.ibm.ws.cluster.router.selection.SelectionManager.handleRemot
    eException(SelectionManager.java:629)
    at
    com.ibm.ws.cluster.router.selection.WLMClientForCommonRouterImpl
    .handleRemoteException(WLMClientForCommonRouterImpl.java:414)
    at
    com.ibm.ws.wlm.client.WLMClient.handleRemoteException(WLMClient.
    java:237)
    at
    com.ibm.rmi.corba.ClientDelegate.invoke(ClientDelegate.java:524)
    at
    com.ibm.CORBA.iiop.ClientDelegate.invoke(ClientDelegate.java:123
    8)
    at
    com.ibm.rmi.corba.ClientDelegate.invoke(ClientDelegate.java:708)
    at
    com.ibm.CORBA.iiop.ClientDelegate.invoke(ClientDelegate.java:126
    8)
    at
    org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:484)
    at test.ibm.some_Stub.create(some_Stub.java:215)
    at sun.reflect.GeneratedMethodAccessor192.invoke(Unknown Source)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
    AccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Hung thread SystemOut messages          *
    *                      indicating java.util.HashMap thread     *
    *                      hang in UnavailableManagerImpl          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Use of java.util.HashMap in UnavailableManagerImpl was not
    thread safe and led to hung threads. This was updated to
    implement java.util.ConcurrentHashMap instead to ensure thread
    safety.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI20776

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-06-25

  • Closed date

    2014-10-28

  • Last modified date

    2014-10-28

  • 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



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PI20776

Modified date: 28 October 2014