Hi,
Tim Yates wrote:
> > If your are using the Minerva pools, please be
> > aware that the real DB connection is being held
> > internally until the transaction is also
> > terminated.
>
> > Real XA datasources do not have this problem.
>
> What is the real XAdatasource for Oracle 8i?
JDBC2.0-stdext or JDBC3.0 XA data sources. These
are the JDBC standards that J2EE were meant to
use.
The Minerva XA datasource is a hack that enables
old non-XA datasources, but it has some problems.
I don't know where you get this for Oracle, but I
know it exists. Aaron Mulder did some hacks to the
transaction system to make it possible to run 8.1.6
XA datasource despite the incompatibilities this
driver has.
I have heard that it is better with the 8.1.7
driver, but I am not a Oracle user...
> Hmmm...confused by this last post (doesn't take much on a Sunday afternoon
> though :p)
Ok, I'll try to explain: Transactions generally
live longer than the datasource is open. For a
non-XA JDBC connection you (or more precisely:
Minerva) can either commit or rollback the work
done on the connection. But until the transaction
is committed or rolled back, Minerva does not know
if it should commit or rollback on the JDBC
connection. So Minerva holds on to it (without
closing it) until the transaction is terminated.
Hope this clarifies, otherwise let me know.
Best Regards,
Ole Husgaard.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
