PQ56858: TRANSACTIONABORTEDEXCEPTION THROWN BY WEBSPHERE 3.5.4 WITH ORACLE 8.1.7 JDBC DRIVER(JTA-ENABLED)

A fix is available
3.5.4-3.5.7, 4.0.2-4.0.7: Component cumulative Connection Manager fix

APAR

APAR status
Closed as program error.

Error description
When using WAS 3.5.4 with JTA-enabled Oracle 8.1.7 JDBC driver,
customer sees TransactionAbortedException when a transaction is
made to the database.  CM/JTS trace shows that the driver is
being read as an Oracle 8.1.6 driver.
KEYWORDS: Websphere WAS 3.5 3.5.4 JTA Oracle 35 354 817 8.1.7
Local fix
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of Oracle *
*                 as their Database.                           *
****************************************************************
* PROBLEM DESCRIPTION: When using WAS JTA Oracle 8.1.7 JDBC    *
*                      driver, a TransactionAbortedException   *
*                      is seen.                                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When using WAS 3.5.4 with JTA-enabled Oracle 8.1.7 JDBC driver,
customer sees TransactionAbortedException when a transaction is
made to the database.  CM/JTS trace shows that the driver is
being read as an Oracle 8.1.6 driver.
Problem conclusion
User sets DataSource for Oracle database to JTA enabled and
then uses the datasource with either BMP or servlet.  For
Oracle, the transaction isolation level must be set to
TRANSACTION_READ_COMMITTED when using an XAConnection (i.e.
JTA enabled datasource) otherwise the xa_start will fail, which
causes transactions to throw transaction aborted.  Note that
CMPs do not have this problem because we tell the user to
set the CMP to TRANSACTION_READ_COMMITTED when using the CMP
with JTA enabled Oracle datasource.
.
The code will detect when a two-phase commit is being
done and the Oracle specific code will change the isolation
level to TRANSACTION_READ_COMMITTED insted of the current
default of TRANSACTION_SERIALIZABLE.
Temporary fix
Comments
APAR information
APAR numberPQ56858
Reported component nameWAS ADVANCED SU
Reported component ID5648C8402
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2002-01-18
Closed date2002-03-21
Last modified date2002-03-21

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:


Modules/Macros
JDBC
APAR is sysrouted TO one or more of the following:Modules/Macros

Fix information
Fixed component nameWAS ADVANCED SU
Fixed component ID5648C8402

Applicable component levels
R350 PSYUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ56858
IBM Group: Software Group
Modified date: 2002-03-21