PK20056: THE TRANSACTION IS TAKING MORE TIME THAN THE TRANSACTION TIMEOUTSETTING OF 120 SECONDS.

 Fixes are available

5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for AIX
5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for HP-UX
5.1.1.19: WebSphere Application Server V5.1.1 Cumulative Fix 19 for Linux
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for AIX
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for AIX
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for HP-UX
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for Solaris
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for Windows
PK20056; 5.1.1.9: the transaction is taking more time than transaction timeout
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for Linux
5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for Linux
5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for Solaris
5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for Windows
5.1.1.19: WebSphere Application Server V5.1.1 Cumulative Fix 19 for AIX
5.1.1.19: WebSphere Application Server V5.1.1 Cumulative Fix 19 for Windows
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for AIX
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for Windows
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for Windows
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for Solaris
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for Linux
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for Windows
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for Solaris
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for AIX
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for Linux
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for HP-UX
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for Solaris
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for Solaris
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for AIX
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for Windows
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for HP-UX
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for Solaris
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for Solaris
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for Linux
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for AIX
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for Linux
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for Windows
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for Windows
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for HP-UX
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for HP-UX
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for AIX
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for HP-UX
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for HP-UX
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for Linux
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for Linux
5.1.1.19: WebSphere Application Server V5.1.1 Cumulative Fix 19 for HP-UX



APAR status
Closed as program error.

Error description
The transaction is taking more time than the transaction timeout
setting of 120 seconds.

In handling the timeout, we issue a rollbackResources call -
this is meant to rollback the local resources only.  However,
the call is sent to remote servers involved in the transaction
erroneously.  So when requests come in from a remote server, the
remote server attempts to register with the tran service again.
This leads to an error being detected in TxClientInterceptor and
the code tries to rollback the transaction twice.  In doing so,
it makes two calls to resumeAssociation which causes an
indefinite hang.


  1/21/06 16:33:17:260 CST 5c0ea073 TranManagerIm I WTRN0041I:
   Transaction
  57415344:00000000000005a3000000029a0e240f469ec1
  058bc60c8db405097be527e8976270655f636c6f5f3031■ has been
  rolled back.
  1/21/06 16:33:18:422 CST 5c0ea073 ExceptionUtil E CNTR0019E:
  Non-application exception occurred while processing method
  "query". Exception data:  com.ibm.websphere.csi.CSITransaction
  RolledbackException: Transaction rolled back; nested
  exception is:
  javax.transaction.TransactionRolledbackException:
  Transaction is ended due to timeout
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server version 5.1 *
*                 users.                                       *
****************************************************************
* PROBLEM DESCRIPTION: A distributed transaction may hang      *
*                      after the transaction times out         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Distributed transaction may hang after the transaction times
out. In this case, a transaction timeout was being handled. As
part of this, we sent a rollback request to subordinate
servers involved in the transaction. The remote servers
handled the rollback request correctly. However, a further
request was made to one of the remote servers, which caused
the remote server to attempt to register with the superior
server's transaction service. This led to an error being
detected in TxClientInterceptor and the code tries to rollback
the transaction twice.  In doing so, it makes two calls to
resumeAssociation which causes an indefinite hang.
Problem conclusion
Class TxClientInterceptor will be changed so that when the
second registration is detected, the attempt to rollback the
transaction will be made only once.

The fix for this APAR is currently targeted for inclusion in
fixpack 5.1.1.11.  Please refer to the Recommended Updates
page for delivery information:

http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

This APAR is not applicable to version 6 of WebSphere
Application Server.
Temporary fix Comments
APAR information
APAR number PK20056
Reported component name WAS NETWRK DEPL
Reported component ID 5630A3601
Reported release 10A
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2006-02-20
Closed date 2006-03-24
Last modified date 2006-03-24

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
TXCLNTIN          

Publications Referenced

Fix information
Fixed component name WAS NETWRK DEPL
Fixed component ID 5630A3601

Applicable component levels
R003 PSN    UP
R00A PSN    UP
R00H PSN    UP
R00I PSN    UP
R00P PSN    UP
R00S PSN    UP
R00W PSN    UP
R103 PSY    UP
R10A PSY    UP
R10H PSY    UP
R10I PSY    UP
R10P PSY    UP
R10S PSY    UP
R10W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 10A
Software edition:
Reference #: PK20056
IBM Group: Software Group
Modified date: Mar 24, 2006