Weblogic Migration, JDBC doesn't support XA issue

Question

We are doing Weblogic Migration from WLS10.3.2 to WLS10.3.6 and Java from jdk1.6.0_26 to jdk1.7.0_07
we are facing the following error for two modules which sends email but few other modules sending email are working fine :
javax.transaction.xa.XAException: JDBC driver does not support XA, hence cannot be a participant in two-phase commit. To force this participation, set the GlobalTransactionsProtocol attribute to LoggingLastResource (recommended) or EmulateTwoPhaseCommit for the Data Source = ABATDataSource
*[Wed Apr 10 08:40:03.069,<gzd4qc>] DEBUG (WorkRequestServiceImpl:sentEmailNotification) - Remote Exception occurred : javax.transaction.TransactionRolledbackException: BEA1-0020971AAD25AA29B1E3: javax.transaction.xa.XAException: JDBC driver does not support XA, hence cannot be a participant in two-phase commit. To force this participation, set the GlobalTransactionsProtocol attribute to LoggingLastResource (recommended) or EmulateTwoPhaseCommit for the Data Source = ABATDataSource*
In Weblogic10.3.6, if we change the Datasource --> Transaction from one-phase commit to Logging Last Resource,
this issue is getting resolved.
But all the modules were working fine with one-phase commit in Weblogic10.3.2
Could you kindly help us to fix this issue and problem in migration.

Answer 1

Hi Joe,
We have changed the driver to XA ( Oracle's Driver (Thin XA) for instance connections; Versions:9.0.1 and later )
and we are getting the below issue in below case
CASE:
I will start a transaction and it gets connected to the Database through
the datasource in weblogic server and then it updates the data into the database which was given from the screen
Issue:
Caused by: java.sql.SQLException: Connection closed
at weblogic.jdbc.wrapper.JTAConnection.getXAConn(JTAConnection.java:213)
at weblogic.jdbc.wrapper.JTAConnection.checkConnection(JTAConnection.java:84)
at weblogic.jdbc.wrapper.ResultSetMetaData.preInvocationHandler(ResultSetMetaData.java:61)
at weblogic.jdbc.wrapper.ResultSetMetaData_oracle_jdbc_driver_OracleResultSetMetaData.getColumnCount(Unknown Source)
Hence i think i cannot go for XA driver....
It is working for Non XA driver with Logging Last Resource
As per your note
Logging Last Resource is an excellent way to engage one non-XA
resource in a global transaction, with complete safety. The LLR resource is used for logging the
XA transaction, and is committed as the first part of the second phase of the commit. As such it
can be managed XA-wise whether that succeeds or fails.
Can i keep as LLR itself
Will there be any impact for my applications for below transaction scenarios ?
One case
I will start a transaction and it gets connected to the Database through
the datasource in weblogic server and then it updates the data into the database which was given from the screen
Another case
I will start a transaction and it gets connected to the Database(2) through the datasource(2) in weblogic server and it
reads the data from database(2) and then it updates the data(which was read) into database(1)
I am also using EJB 3.0 version ( transaction-type - Container and Bean. Session-type - Stateless )
Note the changes
Previous Datasources details
X datasource points to a my db - Non XA driver with one phase commit
Y datasource points to a other db - Non XA driver with one phase commit
Issue :
javax.transaction.xa.XAException: JDBC driver does not support XA, hence cannot be a participant in two-phase commit. To force this participation, set the GlobalTransactionsProtocol attribute to LoggingLastResource (recommended) or EmulateTwoPhaseCommit for the Data Source = ABATDataSource
[Wed Apr 10 08:40:03.069,<gzd4qc>] DEBUG (WorkRequestServiceImpl:sentEmailNotification) - Remote Exception occurred : javax.transaction.TransactionRolledbackException: BEA1-0020971AAD25AA29B1E3: javax.transaction.xa.XAException: JDBC driver does not support XA, hence cannot be a participant in two-phase commit. To force this participation, set the GlobalTransactionsProtocol attribute to LoggingLastResource (recommended) or EmulateTwoPhaseCommit for the Data Source = ABATDataSource
Changed Datasources details
X datasource points to a my db - Non XA driver with LLR
Y datasource points to a other db - Non XA driver with one phase commit
Working
Can you please provide ur advise . thanks
Thanks and Regards
K.Vickram