PK20056: THE TRANSACTION IS TAKING MORE TIME THAN THE TRANSACTION TIMEOUTSETTING OF 120 SECONDS. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() 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 timeoutLocal 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 is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
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
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.