PK55248: WTRN0080W IN THE REMOTE SERVER WHEN REMOTE SERVER IS RECYCLED INBETWEEN TRANSACTIONS. | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description WebSphere for z/OS application server hosts a servlet which 1) creates a user transaction 2) invokes a remote EJB 3) performs a commit or rollback upon completion of the remote EJB - When the remote server hosting the remote EJB is recycled, then various results are observed during the next servlet execution in the WebSphere for z/OS application server. - - If the servlet does commit() upon completion of the remote EJB call, then WebSphere for z/OS logs the following error throws a CORBA::TRANSACTION_ROLLEDBACK exception with minor code C9C218C5: - Trace: 2007/07/12 02:38:15.929 01 t=7CB280 c=UNK key=P8 (13007002) ThreadId: 00000023 FunctionName: com.ibm.ws390.tx.TransactionMessagePipe SourceId: com.ibm.ws390.tx.TransactionMessagePipe Category: FINE ExtendedMessage: getExceptionCode; 28 Trace: 2007/07/12 02:38:15.930 01 t=7CB280 c=UNK key=P8 (00000004) Description: Throw CORBA system exception exception id: CORBA::TRANSACTION_ROLLEDBACK minor code: c9c218c5 from filename: ./bbgtjexh.cpp at line: 604 - - If the servlet does rollback() then the TransactionMessagePipe takes about 60 seconds to complete: - Trace: 2007/07/12 07:20:29.741 01 t=7CB280 c=UNK key=P8 (13007002) ThreadId: 00000023 FunctionName: processTmp SourceId: com.ibm.ws390.tx.NativeTransactionContext Category: FINER ExtendedMessage: Entry; com.ibm.ws390.tx.TransactionMessagePipe@49d Trace: 2007/07/12 07:21:34.284 01 t=7CB280 c=UNK key=P8 (13007002) ThreadId: 00000023 FunctionName: processTmp SourceId: com.ibm.ws390.tx.NativeTransactionContext Category: FINER ExtendedMessage: Exit; com.ibm.ws390.tx.TransactionMessagePipe@5b07 - - In each case the remote server logs WTRN0080W message after completing the EJB method.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V6.1 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: When transactions are active between * * a WebSphere Application Server for z/OS * * version 6.1 server (A) that is acting * * as a client and a remote WebSphere * * Application Server (B), if the remote * * server (B) is recycled between * * requests the transaction for the next * * outbound request (from A to B) will be * * rolled back. * **************************************************************** * RECOMMENDATION: * **************************************************************** When an established outbound connection from a WebSphere Application Server for z/OS version 6.1 server is broken, the stale connection may not be detected until the next time an outbound request message is sent. In this case, an exception raised because of the bad/stale outbound connection prevented a permissible retry of the outbound request, causing the transaction rollback.Problem conclusion In outbound request processing, an additional test was added to ensure that exceptions encountered while preparing an outbound request does not prevent the outbound request from being retried. APAR PK55248 is currently targeted for inclusion in Service Level (Fix Pack) 6.1.0.15 of WebSphere Application Server V6.1 for z/OS.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
|
Document Information |
Current web document: swg1PK55248.html
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 610
Software edition:
Reference #: PK55248
IBM Group: Software Group
Modified date: Apr 1, 2008
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.