*Note* I saw a howto in the manual and the only differnece between it and
what I currently
have is add the following line to jboss.properties
jboss.xa.xidclass=oracle.jdbc.xa.OracleXid
So is this what you are talking about?
I cam confused because, I noticed that the it still uses the wrapper(See
below).
..jboss.jcml
<attribute
name="DataSourceClass">org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl</attr
ibute>
..jboss.jcml
-----Original Message-----
From: Ole Husgaard [mailto:[EMAIL PROTECTED]]
Sent: Saturday, September 22, 2001 5:09 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Transaction Exception !!! / ejbStore
Hi,
"Ferguson, Doug" wrote:
>
> I've done some more research and it appears that there is alittle more
going
> on.
>
> We have two datasources. 1 is for failover.
> The 2nd database syncs with the other every 10 minutes.
> For our user session we have to write to both of the databases.
> This wier exception was occuring when both databases were set to the same
> database.
>
> Note: Could this be because jBoss sees the databases as different but they
> are actually the same?
I guess so. In that case, the commit would happen twice on the
same database.
I have to warn against using the XA wrapper with more than one
datasource:
Problem is that the XA prepare step is a no-op in the wrapper,
so the commit step is not guaranteed to succeed.
So the TM could do the commit step fine on the first datasource,
and if the commit step fails on the second data source you end
up with a heuristic, and your data integrity is void.
To get around that problem, use _real_ XA datasources, without
the wrapper.
Best Regards,
Ole Husgaard.
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
