JTAXA resource problem using Oracle 8.1.7 driver with WAS 3.5.4
Yeong Kim
throws the following error attached below. (We're using WebSphere 3.5.4 and
Oracle 8.1.7.) Basically it indicates that an error occurred while creating
XA connection and XA resource to Oracle because no suitable driver was
available. Currently, I'm using Oracle thin driver,
oracle.jdbc.driver.OracleDriver (with JTA-enabled flag).
After this, whenever ds.getConnection() is attempted, WebSphere throws a
'JTS/JTA transaction aborted' exception. Does anybody know what is
triggering this, and a possible way to resolve this problem?
Thanks for your help,
Yeong
****************************************************************************
*******************************************
[01.11.23 13:40:04:365 EST] e63caf OraJTAXAResou W Encountered an error
while creating XA connection and XA resource java.sql.SQLException: No
suitable driver
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Compiled Code)
at java.sql.SQLException.<init>(SQLException.java:64)
at java.sql.DriverManager.getConnection(Compiled Code)
at java.sql.DriverManager.getConnection(DriverManager.java:137)
at
oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:111)
at
oracle.jdbc.pool.OracleConnectionPoolDataSource.getPhysicalConnection(Oracle
ConnectionPoolDataSource.java:107)
at
oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.
java:88)
at
com.ibm.ejs.jts.jta.factory.OraJTAXAResourceFactory.getXAResource(OraJTAXARe
sourceFactory.java:71)
at com.ibm.ejs.jts.jta.JTSXA.recover(Compiled Code)
at
com.ibm.ejs.jts.jta.recovery.XARecoveryManager.xaRestartRecovery(Compiled
Code)
at
com.ibm.ejs.jts.jta.recovery.XARecoveryManager.duringRestart(XARecoveryManag
er.java:210)
at com.ibm.ejs.jts.tran.Tran.ready(Compiled Code)
at com.ibm.ejs.jts.jts.CurrentSet.ready(CurrentSet.java:159)
at com.ibm.ejs.jts.jts.Jts.ready(Jts.java:132)
at com.ibm.ejs.sm.server.ManagedServer.initializeTran(Compiled Code)
at
com.ibm.ejs.sm.server.ManagedServer.initializeRuntime(ManagedServer.java:574
)
at com.ibm.ejs.sm.server.ManagedServer.main(ManagedServer.java:140)
[01.11.23 13:40:04:411 EST] e63caf JTSXA W Can not create XAResource
object
Strange Anomaly
I think this is because of the tran logs. open a pmr. or if you have a
copy of fresh tranlog then you can back up your current one and then
copy over it. There are 2 files. files are called tran1.log and
tran2.log or tran_<node name>/log
Yeong Kim
resolve the "error occurred while creating
XA connection and XA resource to Oracle because no suitable driver was
However, I'm still getting the "JTS/JTA transaction has been aborted"
exception when ds.getConnection() is attempted within an transaction
context, as attached below. (Outside txn, it is OK.) Looking at the stack
trace, the exception is coming from the WebSphere class; there is no Oracle
involved here. Again, I'm using the Oracle thin driver with JTA enabled. Any
idea on how to resolve this problem?
Thanks,
Yeong
>>[08:41:49 EST]
com.statestreet.sle.esi.communication.dispatcher.MessageDispatcherEJB >> in
ds.getConnection()/Exception branch,
e:com.ibm.ejs.cm.exception.TransactionAbortedException: JTS/JTA transaction
has been aborted
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Compiled Code)
at java.sql.SQLException.<init>(SQLException.java:82)
at
com.ibm.ejs.cm.portability.PortableSQLException.<init>(PortableSQLException.
java:35)
at
com.ibm.ejs.cm.exception.TransactionAbortedException.<init>(TransactionAbort
edException.java:8)
at com.ibm.ejs.cm.pool.JTAConnectO.enlist(Compiled Code)
at com.ibm.ejs.cm.pool.ConnectO.allocate(ConnectO.java:380)
at
com.ibm.ejs.cm.pool.ConnectionPool.allocateConnForTransaction(ConnectionPool
.java:616)
at com.ibm.ejs.cm.pool.ConnectionPool.findConnectionForTx(Compiled
Code)
at
com.ibm.ejs.cm.pool.ConnectionPool.allocateConnection(ConnectionPool.java:50
7)
at
com.ibm.ejs.cm.pool.ConnectionPool.getConnection(ConnectionPool.java:220)
at
com.ibm.ejs.cm.DataSourceImpl.getConnection(DataSourceImpl.java:113)
at
com.statestreet.sle.esi.communication.dispatcher.MessageDispatcherEJB.getCon
nection(MessageDispatcherEJB.java:329)
at
com.statestreet.sle.esi.communication.dispatcher.MessageDispatcherEJB.testJD
BC(Compiled Code)
at
com.statestreet.sle.esi.communication.dispatcher.MessageDispatcherEJB.putMes
sage(MessageDispatcherEJB.java:50)
at
com.statestreet.sle.esi.communication.dispatcher.EJSRemoteMessageDispatcher.
putMessage(EJSRemoteMessageDispatcher.java:62)
at
com.statestreet.sle.esi.communication.dispatcher._MessageDispatcher_BaseStub
.putMessage(_MessageDispatcher_BaseStub.java:304)
at
com.statestreet.sle.esi.communication.dispatcher._MessageDispatcher_Stub.put
Message(Compiled Code)
at
com.statestreet.sle.esi.communication.listener.MQJMSMessageListener.processM
essage(MQJMSMessageListener.java:236)
at
com.statestreet.sle.esi.communication.listener.MQJMSMessageListener.onMessag
e(MQJMSMessageListener.java:150)
at com.ibm.mq.jms.MQQueueReceiver.receiveAsync(Compiled Code)
at com.ibm.mq.jms.SessionAsyncHelper.run(Compiled Code)
:
>>[08:41:49 EST]
com.statestreet.sle.esi.communication.dispatcher.MessageDispatcherEJB >>
returned conn:null:
"Strange Anomaly" <s...@sa.com> wrote in message
news:3C0567DF...@sa.com...
Chris Day
driver for JTA/XA. Are you using the right JDBC drivers for Oracle,
JTA/XA wasn't supported at 8.1.6. Also, are you aware of the
limitations of using JTA/XA with XA? The infocenter says that JTA/XA
with Oracle is only supported by CMP entity beans. IBM say this is
down to bugs in the Oracle JDBC drivers.
Chris