IBM Support

PM49633: DEADLOCK ON SIB JS-RECEIVELISTENERDISPATCHERTHREADS

Fixes are available

8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
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.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
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.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
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.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 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

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Deadlock between JS-ReceiveListenerDispatcherthreads causes
    hang.
    .
    When the deadlock occurs, a thread dump from the application
    server will show one or more threads blocked in the method
    com/ibm/ws/sib/comms/server/clientsupport/
    ServerTransportAcceptListener.removeAllConversations().  In
    order for this APAR to match, another thread must be blocked in
    the method com/ibm/ws/sib/jfapchannel/impl/
    Connection.getConnectionClosedListener().
    
    Javacore shows the following symptom:
    
    1LKDEADLOCK    Deadlock detected !!!
    NULL           ---------------------
    NULL
    2LKDEADLOCKTHR  Thread "JS-ReceiveListenerDispatcher : 2335"
    (0x0000000002578400)
    3LKDEADLOCKWTR    is waiting for:
    4LKDEADLOCKMON      sys_mon_t:0x000000001E3525F0 infl_mon_t:
    0x000000001E352660:
    4LKDEADLOCKOBJ
    java/lang/Object@0x00000000BFE8A080/0x00000000BFE8A08C:
    3LKDEADLOCKOWN    which is owned by:
    2LKDEADLOCKTHR  Thread "JS-ReceiveListenerDispatcher : 2317"
    (0x0000000002617100)
    3LKDEADLOCKWTR    which is waiting for:
    4LKDEADLOCKMON      sys_mon_t:0x00000000229AF480 infl_mon_t:
    0x00000000229AF4F0:
    4LKDEADLOCKOBJ
    java/util/HashMap@0x00000000613276D8/0x00000000613276E4:
    3LKDEADLOCKOWN    which is owned by:
    2LKDEADLOCKTHR  Thread "JS-ReceiveListenerDispatcher : 2335"
    (0x0000000002578400)
    
    JS-ReceiveListenerDispatcher : 2335
    
    at
    com/ibm/ws/sib/jfapchannel/impl/Connection.getConnectionClosedLi
    stener(Connection.java:1651(Compiled Code)) at
    com/ibm/ws/sib/jfapchannel/impl/ConversationImpl.getConnectionCl
    osedListener(ConversationImpl.java:1814(Compiled Code)) at
    com/ibm/ws/sib/comms/server/clientsupport/ServerTransportAcceptL
    istener.acceptConnection(ServerTransportAcceptListener.java:127(
    Compiled Code)) at
    ..
    
    
    JS-ReceiveListenerDispatcher : 2317
    
    at
    com/ibm/ws/sib/comms/server/clientsupport/ServerTransportAcceptL
    istener.removeAllConversations(ServerTransportAcceptListener.jav
    a:264(Compiled Code)) at
    com/ibm/ws/sib/comms/server/clientsupport/ServerSideConnection.c
    onnectionClosed(ServerSideConnection.java:384) at
    com/ibm/ws/sib/jfapchannel/impl/Connection.notifyCloseListeners(
    Connection.java:1305(Compiled Code)) at
    com/ibm/ws/sib/jfapchannel/impl/Connection.nonThreadSafePhysical
    Close(Connection.java:1075(Compiled Code)) at
    com/ibm/ws/sib/jfapchannel/impl/Connection.physicalCloseFromInva
    lidateImpl(Connection.java:946) at
    com/ibm/ws/sib/jfapchannel/impl/InboundConnection.invalidateImpl
    (InboundConnection.java:173) at
    ..
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the default messaging provider     *
    *                  for IBM WebSphere Application Server        *
    ****************************************************************
    * PROBLEM DESCRIPTION: Deadlock between                        *
    *                      JS-ReceiveListenerDispatcher threads.   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The locking implementation for the JS-ReceiveListenerDispatcher
    threads was incorrect, and did not properly conform to the
    locking heirarchy. Under some timing conditions this could lead
    to a deadlock.
    

Problem conclusion

  • The code has been altered to adher to the locking heirarchy to
    ensure the deadlock condition is avoided.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 7.0.0.23 and 8.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

    PM49633

  • Reported component name

    WAS SIB & SIBWS

  • Reported component ID

    620800101

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-10-07

  • Closed date

    2011-10-31

  • Last modified date

    2011-10-31

  • 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 SIB & SIBWS

  • Fixed component ID

    620800101

Applicable component levels

  • R800 PSY

       UP



Document information

More support for: WebSphere Application Server
Service Integration Technology

Software version: 7.0

Reference #: PM49633

Modified date: 31 October 2011