IBM Support

PM74709: DEADLOCK DETECTED IN WEBSPHERE APPLICATION SERVER SERVICE INTEGRATION BUS MESSAGING ENGINE

Fixes are available

8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
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.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.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

  • Messages are sometimes stuck in locked state on WebSphere
    Application Server Service Integration Bus messaging engine
    destination. Once the messages are stuck all subsequent
    messages are not processed and even after removing the locked
    message, the subsequent messages remain stuck without being
    processed.
    
    
    javacores show deadlock between the following threads:
    
    Deadlock detected !!!
    ---------------------
    
    Thread "WorkManager.DefaultWorkManager : 1" (0x08F5C500)
    is waiting for:
    sys_mon_t:0x08ED37CC infl_mon_t: 0x08ED3804:
    com/ibm/ws/sib/processor/impl/AsynchConsumer@0x9B6401D8/0x9B6401
    E4:
    which is owned by:
    2LKDEADLOCKTHR  Thread "Consumer XXX : 870" (0x8D366500)
    which is waiting for:
    sys_mon_t:0x08ED3820 infl_mon_t: 0x08ED3858:
    com/ibm/ws/sib/ra/inbound/impl/SibRaListener$3@0x9B63FA68/0x9B63
    FA74:
    which is owned by:
    Thread "WorkManager.DefaultWorkManager : 1" (0x08F5C500)
    
    Thread WorkManager.DefaultWorkManager : 1
    
    at com/ibm/ws/sib/processor/impl/JSLocalConsumerPoint.
    internalStart(JSLocalConsumerPoint.java:3663)
    at com/ibm/ws/sib/processor/impl/JSLocalConsumerPoint.start
    (JSLocalConsumerPoint.java:3647)
    at com/ibm/ws/sib/processor/impl/ConsumerSessionImpl.start
    (ConsumerSessionImpl.java:855)
    at com/ibm/ws/sib/ra/inbound/impl/SibRaListener.startSession
    (SibRaListener.java:1218)
    at com/ibm/ws/sib/ra/inbound/impl/SibRaSingleProcessListener$
    SibRaWork.workEnded(SibRaSingleProcessListener.java:749)
    at com/ibm/ws/sib/ra/inbound/impl/SibRaSingleProcessListener$
    SibRaWork.workCompleted(SibRaSingleProcessListener.java:708)
    at org/springframework/jca/work/SimpleTaskWorkManager$Delegating
    WorkAdapter.run(SimpleTaskWorkManager.java:244)
    at org/springframework/scheduling/commonj/DelegatingWork.run
    (DelegatingWork.java:61)
    at com/ibm/ws/asynchbeans/J2EEContext.run(J2EEContext.java:
    1150)
    at com/ibm/ws/asynchbeans/WorkWithExecutionContextImpl.go
    (WorkWithExecutionContextImpl.java:199)
    at com/ibm/ws/asynchbeans/CJWorkItemImpl.run
    (CJWorkItemImpl.java:188)
    at com/ibm/ws/util/ThreadPool$Worker.run
    (ThreadPool.java:1613)
    
    Thread Consumer XXX : 870:
    
    at com/ibm/ws/sib/ra/inbound/impl/SibRaListener.consume
    Messages(SibRaListener.java:932(Compiled Code))
    at com/ibm/ws/sib/processor/impl/AsynchConsumer.processMsgs
    (AsynchConsumer.java:113(Compiled Code))
    at com/ibm/ws/sib/processor/impl/JSLocalConsumerPoint.process
    AttachedMsgs(JSLocalConsumerPoint.java:2518(Compiled Code))
    at com/ibm/ws/sib/processor/impl/JSLocalConsumerPoint.run
    AsynchConsumer(JSLocalConsumerPoint.java:3293(Compiled Code))
    at com/ibm/ws/sib/processor/impl/JSLocalConsumerPoint$Asynch
    Thread.run(JSLocalConsumerPoint.java:3588(Compiled Code))
    at com/ibm/ws/util/ThreadPool$Worker.run(ThreadPool.java:
    1613(Compiled Code))
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the default messaging provider     *
    *                  for IBM WebSphere Application Server        *
    *                  Version 7.0, 8.0 and 8.5.                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: Messages remain stuck without being     *
    *                      processed by MDB due to deadlock.       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Deadlock detected in Resouce Adapter (RA) code when concurrent
    instances of an MBD are consuming messages. As per the
    javacore, the state of the threads is as follows.
    Thread1:
    waiting for lock2 at JSLocalConsumerPoint.internalStart()
    obtained lock1 at
    SibRaSingleProcessListener$SibRaWork.workEnded()
    Thread2:
    waiting for lock1 at SibRaListener.consumeMessages()
    obtained lock2 at JSLocalConsumerPoint.runAsynchConsumer()
    Fix for this problem is to have a check and not to acquire
    lock1 in consumeMessages() if the session is starting.
    

Problem conclusion

  • Source code has been modified not to consume messages if
    the session starting is in progress.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.27, 8.0.0.6 and 8.5.0.2.  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

    PM74709

  • 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

    2012-10-10

  • Closed date

    2012-12-05

  • Last modified date

    2012-12-05

  • 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 #: PM74709

Modified date: 05 December 2012