Problem configuring Oracle for XA Recovery

[abonfield]

I have been trying to configure JBoss 4.2.2GA to get XA recovery to work.
I have looked at the documentation but I am still struggling.

I want to be able to configure an database connection that automatically enlists and recovers.
What is the recommended way of doing this?

Having read the documentation that says:

Note: if using the transactional JDBC 2.0 driver provided with JBossJTA, then
no additional work is necessary in order to ensure that recovery occurs.

I then set the following datasource properties


<local-tx-datasource>
<jndi-name>TCConfigDB</jndi-name>
<connection-url>jdbc:arjuna:jdbc:oracle:thin:@localhost:1521:ORCL9i</connection-url>
<driver-class>com.arjuna.ats.jdbc.TransactionalDriver</driver-class>
<connection-property name="DYNAMIC_CLASS">oracle.jdbc.OracleDriver</connection-property>
<user-name>username</user-name>
password
</local-tx-datasource>

this lead to the following error on start up:


15:24:44,660 WARN [logger] [com.arjuna.ats.internal.jdbc.nojdbc3] Can't load JDBC 3.0 wrapper, falling back to JDBC 2.0: java.util.Hashtable$EmptyEnumerator@de
a70b
15:24:44,676 ERROR [STDERR] java.lang.ClassCastException: oracle.jdbc.OracleDriver
15:24:44,676 ERROR [STDERR] at com.arjuna.ats.internal.jdbc.DirectRecoverableConnection.createConnection(DirectRecoverableConnection.java:393)
15:24:44,676 ERROR [STDERR] at com.arjuna.ats.internal.jdbc.DirectRecoverableConnection.getConnection(DirectRecoverableConnection.java:301)
15:24:44,676 ERROR [STDERR] at com.arjuna.ats.internal.jdbc.ConnectionImple.getConnection(ConnectionImple.java:584)
15:24:44,676 ERROR [STDERR] at com.arjuna.ats.internal.jdbc.ConnectionImple.getTransactionIsolation(ConnectionImple.java:448)
15:24:44,676 ERROR [STDERR] at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.(BaseWrapperManagedConnection.java:98)
15:24:44,676 ERROR [STDERR] at org.jboss.resource.adapter.jdbc.local.LocalManagedConnection.(LocalManagedConnection.java:47)
15:24:44,676 ERROR [STDERR] at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:175)
15:24:44,676 ERROR [STDERR] at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:577)
15:24:44,676 ERROR [STDERR] at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:262)
15:24:44,676 ERROR [STDERR] at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:500)
15:24:44,676 ERROR [STDERR] at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:341)
15:24:44,676 ERROR [STDERR] at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:315)
15:24:44,676 ERROR [STDERR] at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:396)
15:24:44,676 ERROR [STDERR] at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:842)
15:24:44,676 ERROR [STDERR] at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:88)


Debugging the code this is because it is being cast to a DynamicClass.




Previously I had also tried modifying jbossjta-properties.xml to use the JDBCXARecovery class.





.......

but this also led to a ClassCastException, where the JBoss wrapper datasource failed to be cast to XADataSource
Classcast at JDBCXARecovery line 174

The solution needs to be able to work with Oracle and also with other databases, which is why I have stayed clear of the OracleXARecovery class.


Please could someone enlighten me regarding the recommended way of doing this (including a configuration example please!)


Thanks in advance


Andrew

[jhalliday]

The TransactionDriver is relevant only when using JBossTS outside of the app server. For transactional datasources within the AS, see http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigDataSources

[paulhilliar]

Having followed the instructions on how to setup an XA datasource, we found that recovery of in-doubt Oracle transactions was not happening, which is what led us to try some poking around.

Should XA recovery work 'out of the box' on an Oracle datasource? (configured as per http://wiki.jboss.org/wiki/Wiki.jsp?page=SetUpAOracleDatasource)

Regards

Paul (working with Andy on this problem)

[jhalliday]

For a stock AS 4.2.2.GA server with xa-datasource for Oracle, recovery should be automatic. What versions of Oracle server its JDBC driver are you using? What is the test case you are using? From the server logs, do you see the recovery attempt to run and fail, or not run at all?

[abonfield]

I am using Oracle 9i with the 10.2.0.1.0 JDBC driver classes.
I created a clean installation of AS 4.2.2.GA.
I then set up an xa-datasource as described here:
http://wiki.jboss.org/wiki/Wiki.jsp?page=SetUpAOracleDatasource
I also set the Pad=true in conf\jboss-service.xml

I then debugged into the arjuna code and killed the JBoss server between the prepare and the phase 2 commit of the transaction.
The Oracle transaction was then held in doubt.
The transaction logs had been created under JBOSS_HOME?server\default\data\tx-object-store

When I restarted the server I got the following message as JBoss tried to recover.
"Could not find new XAResource to use for recovering non-serializable XAResource"
It was at this stage that I tried to set up a different configurations of XAResourceRecovery. Should this not be necessary for Oracle then?
What changes need to be made to fix the non-serializable problem?

Should the xa-datasource recovery for Oracle on AS 4.0.5.GA also be automatic?

Thanks in advance.
Andrew

[jhalliday]

4.2.2.GA should recover automatically. I'll look into the issue.

4.0.5.GA has no recovery support at all unless you retrofit it with the JBossTS, in which case the situation is the same as for 4.2.2.GA

[abonfield]

Here is the datasource definition that I am using, in case that helps:


<xa-datasource>
<jndi-name>MyDB</jndi-name>
<track-connection-by-tx>true</track-connection-by-tx>
<isSameRM-override-value>false</isSameRM-override-value>
<xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
<xa-datasource-property name="URL">jdbc:oracle:thin:@localhost:1521:ORCL9i</xa-datasource-property>
<xa-datasource-property name="User">user</xa-datasource-property>
<xa-datasource-property name="Password">password</xa-datasource-property>
<exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name>
<no-tx-separate-pools/>
</xa-datasource>

[abonfield]

Hi jhalliday,

Do you have any updates on this issue?

Regards,
Andrew

[jhalliday]

Nope, I'm working on JTS changes needed for the next AS beta release right now. This is still on my queue, but unless you buy a support contract I can't promise when I'll get to it.

[paulhilliar]

So if we bought a 4.5K support contract, when would we get an answer and if there is a code problem, within what timescale would we get a fix?

[jhalliday]

The support SLA is online at https://www.redhat.com/support/policy/sla/developer/

For something like this I'd figure on 2 business day turnaround for the diagnosis/analysis bit. As for code changes, if required those would probably be rolled into the next EAP cumulative patch (CP) release due at the end of the month.

[marklittle]

This issue may well be relevant too.

[mmusgrov]

"Could not find new XAResource to use for recovering non-serializable XAResource"

This message means that none of the XA Recovery Modules knows about the xid that the TM is trying to recover. Is the transaction in question still in the pending transaction table (DBA_2PC_PENDING) of the database (identified by the datasource TCConfigDB) and is it still pending?.

[scarceller]

I'm having same exact issue, JBossAS V5.0.1 will not recover and in-doubt transaction from Oracle 10g because the TranMgr does not know howto build the recovery connection needed to recover the in-doubt.

Please help, we have tried everything we could think of.

[jhalliday]

> Please help, we have tried everything we could think of.

Which includes configuring AppServerJDBCXARecovery, right? Send me the debug logs and I'll take a look. Better still, upgrade to 5.1.0.GA, rerun the test, then send me the logs from that.