Hi,
> "Bolt, Dave" wrote:
> I've tried the 8.1.7 drivers against the 8.1.6 database both with and without the
> jboss.conf change. The end result is no difference. I've downloaded the 8.1.7 server
> too, but we haven't installed it anywhere as a test.
>
> Another user suggested that I try the OCI driver instead of the thin driver. I've
> placed the following URL in my jboss.jcml file for my datasource
Since Darius Davidavicius has the 8.1.6 OCI driver
working, it must be possible to make that work for
other people.
Darius has classes12.zip in the CLASSPATH, and having
it in the boot class path should work too. However, I
am not sure if declaring it in the MLET will work.
Please try to remove classes12.zip from your MLET
declaration, and add it to your CLASSPATH, or copy
it to lib/ext.
> As another test, we were going to try another DB server (PostGresQL) if we could find
> one that claimed to have true XA support, to see if it really is an Oracle problem.
Being a PostgreSQL user, I had a look at the source
of the early XA driver. It looked to me like it just
did the same hack as the Minerva XA driver shim, so
I stayed with Minerva XA over non-XA PostgreSQL driver.
Don't know if this has changed.
But I guess it should work, except maybe for the
isolation problem if the PostgreSQL XA drivers still
work like the Minerva XA shim.
> The only other issue, is that it could be something in my code. For reference here
>is the
> code that is getting the connection from JNDI. I am turning off autocommit manually,
>because
> I saw somewhere that the pool provided connections with autocommit ON.
It makes sense to turn autocommit off, but that could
also be the source of your problem: The error message
of your second problem indicates that Oracle may be
using some kind of master connection to control the XA
transaction, and hand out subordinate connections to
the user. The transactions in the subordinate
connections would then be nested transactions to the
XA transaction controlled by JBoss and a hidden Oracle
master connection.
Not sure if this is true. But if it is, I guess turning
off autocommit on your connections could result in your
isolation problem.
I would try the OCI driver without changing the
autocommit property of the connections.
Please let us know how this works out, even if your
problems disappear. Seems like there are lots of
people currently having problems with the Oracle XA
datasource.
Best Regards,
Ole Husgaard.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
