Shahar Solomianik wrote:
> 2. do you have "jboss.xa.xidclass=oracle.jdbc.xa.OracleXid" in
> jboss.properties ?
With any of the Oracle 8.1.6 XA drivers, you
need this in jboss.properties.
This is simply a workaround for an
incompatibility in the 8.1.6 drivers.
With the 8.1.7 XA drivers, this incompatibility
has been fixed, so this is no longer needed.
Another 8.1.6 incompatibility was that a JTA
mandated TM optimization made the driver hang,
so in JBoss-2.0-FINAL this optimization is
commented out. The problem was that the 8.1.6
driver would hang when the TM called
start(xid, TMJOIN) on the Oracle XAResource,
so we had to do start(xid, TMNOFLAGS) instead.
This is also fixed in 8.1.7.
In recent CVS, I have changed the TM so that
the optimization is done if (and only if) the
jboss.xa.xidclass property is *not* changed
from the JBoss default.
But in JBoss-2.0-FINAL this optimization is
never done, and I am not sure if that may
cause some problems in the 8.1.7 driver. One
possible problem could be too much isolation,
because the TMJOIN flag tells the Oracle
resource manager that work done on the JDBC
connection should be done in the context of
a transaction that the RM has already seen.
In short:
You need to set property jboss.xa.xidclass
for Oracle 8.1.6 XA drivers *only*.
Best Regards,
Ole Husgaard.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
