PQ56777: XA RECOVERY WITH INDOUBT TRANSACTIONS FOR AN ORACLE DATABASE IS LOOPING | |||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||
APAR status Closed as program error. Error description Using Oracle JDBC 8.1.7 driver for XA DataSource for application in the clone environment, when there are pending transactions, the cloned Application Server couldn't restart. The only way to have the Application Server running is to remove the clone, to recreate the clone, and restart the clone. Once, trying to stop and start the clone again, the problem occurs. . The problem is in XA Recovery with indoubt transactions on an Oracle database. WebSphere attempts to determine if the indoubt transactions on the database belong to this particular server by making XA Recover calls on the database. The calls WebSphere is making conform to the JTA/JTS specification, but Oracle does not support the full JTA/JTS specification, and ignores the parameter that WebSphere passes to. Each time WebSphere calls the database, WebSphere continues to get results even though according to the specification, WebSphere should only get result once. This causes WebSphere to loop. At some later point, WebSphere gets returned a NULL entry which WebSphere is not expecting, thus resulting in the NullPointerException.Local fix Problem summary **************************************************************** * USERS AFFECTED: All WebSphere Application Server V4 users * * using Oracle JTA datasources. * **************************************************************** * PROBLEM DESCRIPTION: When restarting the WebSphere * * Application Server, the restart loops * * and/or fails with * * NullPointerExceptions. Message 'XA * * recover operation: -3' may also be * * reported. * **************************************************************** * RECOMMENDATION: * **************************************************************** On restart, the WebSphere Application Server is attempting to recover transaction information logged with Oracle. It repeatedly calls xa recover to Oracle, as per the JTA/XA specification. Oracle has a single call restriction for this operation.Problem conclusion XARminst will be corrected to detect Oracle datasources during recovery and only make a single xa recover call.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
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ56777
IBM Group: Software Group
Modified date: Jan 24, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.