SessionBroker login fails with Oracle XA

Question

Hi all,
I am trying to use oracle XA with sessionbroker.
I register the session with the session broker and when i try to login it gives
"No suitable driver" error.
Without using session broker, when I get the session, it is working fine.
sb = new SessionBroker();
Project p1 = new CfToplinkMapping();
DatabaseSession orc = p1.createDatabaseSession();
sb.registerSession(SESSION_NAME, orc);
sb.login(); ->>>>>>fails with no suitable driver error...
My project.java contains the following code: -
login.usePlatform(new oracle.toplink.internal.databaseaccess.OraclePlatform());
login.setDriverClassName("oracle.jdbc.xa.client.OracleXADataSource");
login.setConnectionString("jdbc:oracle:thin:@sch1h217:1521:fmstd");
login.setUserName("fms");
login.setEncryptedPassword("8B66EF2A66D659E33500D82AB9562809");
Please let me know where I went wrong. Is there any extra configurations required for XA drivers?

Answer 1

Hi. The issue is that an XA-aware connection can be used at a much finer granularity
than a non-XA connection. XA allows a connection to associate itself for one tx,
make one call, disassociate itself from the tx, and then do a call for another tx.
Therfore the XA connections in the pool may be involved in 1 or more tx's. If your
app is trying to do local tx's as well with these connections, some drivers/DBMSes
get confused.
You can either create a separate pool for non-XA use, or set the keep-connection-till
tx-complete setting for the XA pool. This latter setting will make sure that connections
that are idle in the pool are not associated with any ongoing XA tx.
Joe
Ramamoorthy wrote:
Guys,
I have a problem with JDBC calls with XA Connection Pool (DRIVER:::oracle.jdbc.xa.client.OracleXADataSource).
We are using the same connection pool for EJBs & JDBC calls. When we use JDBC
calls in between EJB calls, we are getting problems.
1) java.sql.SQLException: ORA-02044: transaction manager login denied: transaction
in progress
ORA-06512: at "SYS.JAVA_XA", line 0
ORA-06512: at line 1
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:180)
2) SQL Exception:java.sql.SQLException: XA error: XAER_RMERR : A resource manager
error has occred in the transaction branch start() failed on resource 'XADBPool':
XAER_RMERR : A resource manager error has occured in the transaction branch oracle.jdbc.xa.OracleXAException...
When I changed the DataSource of JDBC calls from XA Connection Pool to Non-XA
connection poll thess errors disappears. I really don't understand the relation
between XA Connection Pool & JDBC calls. Even here my officemates are telling
we should use non-XA connection pool for JDBC. But nobody knows the exact issues..
Please help..
Thanks
Ramamoorthy.