Attached, please fine a patch which fixes problems with Oracle XA driver I have described earlier and example configuration file. The patch is against JBoss_3_0_0 cvs tag (branch?). Hope this helps.
PS: sorry for html posting
-----Original Message-----
From: Igor Fedorenko [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 14, 2002 4:06 PM
To: '[EMAIL PROTECTED]'
Subject: RE: [JBoss-user] XATxConnectionManager with Oracle?
Thanks for a helpful hint, David. As you correctly guessed my test ssb was leaking sql connections. I'll post my patch and config files here shortly.
> -----Original Message-----
> From: David Jencks [mailto:[EMAIL PROTECTED]]
> Sent: Friday, June 14, 2002 2:01 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-user] XATxConnectionManager with Oracle?
>
>
> Thanks for your work on this. Please post the results when you are
> satisfied. IMO the entire xa wrapper needs replacing which I
> unfortunately
> won't have time for soon. I'm not sure if associateConnection can be
> implemented easily. You can avoid it being called if you always close
> connection handles before calling other ejb methods (through
> home or remote
> interfaces) (and do not hold connections over method
> boundaries). So, try
> this:
>
> Connection c = myds.getConnection();
> //do something
> c.close()
> myotherRemoteInterface.doSomethingElse();
> c = myds.getConnection();
> //do the rest of your work
> c.close();
>
> david jencks
>
> On 2002.06.14 13:35:16 -0400 Igor Fedorenko wrote:
> > I spent last two days trying to make this work and it looks
> like there
> > are
> > number of issues with both oracle xa datasource and jboss
> itself. I am
> > getting close to have this configuration work (it's oracle
> 8.1.7.3 in my
> > case but this should not make big difference). Problems that I've
> > seen/fixed
> > so far
> >
> > 1. Oracle xa driver returns difference XAResource for each call to
> > XAConnection.getXAResource (see specs jdbc 2.0, section 7.2.2 why it
> > should
> > not). This problem causes "xaRes not enlisted". Fixed
> XAManagedConnection
> > to
> > cache XAResource, this fix should not break anything else.
> >
> > 2. Although oracle xa driver accepts non-oracle Xid object,
> it seems to
> > require that both getGlobalTransactionId and
> getBranchQualifier always
> > return byte[64], otherwise it throws "invalid transaction id" during
> > XAResource.end. Fixed XidImpl to return such arrays, not
> sure if it will
> > work with all resource managers.
oracle-xa.diff
Description: Binary data
oracle-xa-service.xml
Description: Binary data
