IBM Support

PI13992: DEADLOCK BETWEEN TRANSACTION AND ACTIVITY SERVICES WHEN REMOTE REQUEST TIMES OUT

Fixes are available

7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
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.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
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 deadlock can occur when a transaction and activity loops
    back to the root server and the remote request times out.  One
    of the threads involved in the deadlock will be waiting as
    follows:
    
    Thread "ORB.thread.pool : x" (0000008c) has been active for
    703338 milliseconds and may be hung.  There is/are 3 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:167)
    at
    com.ibm.ws.tx.jta.TransactionImpl.resumeAssociation(TransactionI
    mpl.java:2857)
    at
    com.ibm.ws.Transaction.JTS.TxClientInterceptor.rollbackTransacti
    on(TxClientInterceptor.java:712)
    at
    com.ibm.ws.Transaction.JTS.TxClientInterceptor.receive_common(Tx
    ClientInterceptor.java:346)
    at
    com.ibm.ws.Transaction.JTS.TxClientInterceptor.receive_exception
    (TxClientInterceptor.java:149)
    at
    com.ibm.rmi.pi.InterceptorManager.invokeInterceptor(InterceptorM
    anager.java:583)
    at
    com.ibm.rmi.pi.InterceptorManager.iterateClientInterceptors(Inte
    rceptorManager.java:415)
    at
    com.ibm.rmi.pi.InterceptorManager.iterateReceiveException(Interc
    eptorManager.java:676)
    at
    com.ibm.rmi.corba.ClientDelegate.intercept(ClientDelegate.java:9
    10)
    at
    com.ibm.rmi.corba.ClientDelegate.invoke(ClientDelegate.java:433)
    ...
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  WebSphere Application Server users of the   *
    *                  Activity or Compensation Service            *
    ****************************************************************
    * PROBLEM DESCRIPTION: Threads are hung in the server          *
    *                      with Message WSVR0605W showing a        *
    *                      thread stuck in method                  *
    *                      TransactionImpl.resumeAssociation       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a thread executing under both transaction and activity
    contexts makes requests that loop back to the same server as
    themselves, and then subsequently makes remote requests, a
    deadlock ensues if the initial request times out.  The
    deadlock is between the transaction and activity services.
    This occurs when the thread that initiated the activity
    processes the first remote request's timeout before the other
    threads associated with the same activity have processed the
    repsonses to their own outstanding requests.
    In this case the thread that initiated the activity will first
    associate with the transaction and then will attempt to wait
    for all other threads to disassociate from the activity.
    However to disassocite from the activity, the other
    threads will first need to associate with the transaction when
    processing the response to their own outstanding requests.
    This is a deadlock situation.
    

Problem conclusion

  • The activity service was modified so that the thread that
    initiated the activity temporarily disassociates the
    transaction from the thread while waiting for exclusive access
    to the activity.  This avoids the deadlock.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.35, 8.0.0.10 and 8.5.5.4.  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

    PI13992

  • 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-03-18

  • Closed date

    2014-06-27

  • Last modified date

    2014-06-27

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

Modified date: 27 June 2014