*sigh*
unfortunately a few days ago I also said that using the Oracle XA
datasource was going well, and it was, UNTIL I did the concurrent load
tests. It just didnt work... I hacked the TM code to catch the
OracleXAExceptions
and discovered it was causing the dreaded ORA-600s. We were using
OracleXID, the 8.1.7 classes12.zip against Oracle 8.1.6.2. I wish I had better
news to report. Ive switched back to Minerva (which should be ok for us for
now since we dont really do distributed transactions across multiple databases
yet). Once Minerva was used the application worked well.
its disappointing really, but its what we have come to expect from Oracle
in recent months. We have logged a TAR, but you know how that goes...
cheers
craig
p.s. if anyone can confirm that use of Minerva against a single database
behaves correct transactionally, that would be great!!
At 01:06 PM 1/29/01 +0200, you wrote:
>Hi Tim.
>
>I've tested my CLOB/BLOB OracleXA 8.1.7 issue on high load this morning and
>it throws almost any exception in the book ....
>When I had it working couple of days ago, it worked with several clients,
>probably never having to handle concurrent.
>I feel I have planted vane hopes in everyone hearts saying 8.1.7 xa driver
>did the job ...
>
>The sad thing is that when trying minerva again, things dont go as well,
>too.
>
>Also, anormous combinations off possible test cases (db server/xid class/xa
>datasource/auto commit/select for update/jdbc driver version and type) gets
>me desparate...
>I feel that if we gather all the information we have on this issue in one
>piece it may help us all.
>
>So, assuming you have everything working (with many concurrent users, and no
>matter which workarounds you may have) Can you please reply with whatever
>you know on this issue including :
>1. Oracle version you are using (8.1.6. I believe) ?
>2. do you have "jboss.xa.xidclass=oracle.jdbc.xa.OracleXid" in
>jboss.properties ?
>3. do you use "org.jboss.minerva.xa.XADataSourceImpl" or
>"oracle.jdbc.xa.client.OracleXADataSource" ?
>4. can you post a complete entity bean code that deals with clob/blob ? (to
>see all little stuff that is being discussed lately, such as "setAutoCommit"
>and "select ... for update")
>5. jdbc driver you are using (oci, thin or whatever)
>6. Whatever else you can think about
>
>we WILL have jboss manipulating lobs on oracle !!! (and than we will CMP
>it...)
>
>Shahar.
>
>
>-----Original Message-----
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]]On Behalf Of Tim Yates
>Sent: Monday, January 29, 2001 11:14 AM
>To: jBoss
>Subject: Re: [jBoss-User] JBOSS and Oracle
>
>
>
>From: Ole Husgaard <[EMAIL PROTECTED]>
> > Hi,
> >
> > I would (again) recommend that you do not touch
> > the autoCommit property of your connections.
> > Nobody else does this.
> >
>
>The problem comes if you are using CLOB's or BLOB's, as you have to turn
>auto commit off to select the row for update...
>
>Tim.
>
>
>
>--
>--------------------------------------------------------------
>To subscribe: [EMAIL PROTECTED]
>To unsubscribe: [EMAIL PROTECTED]
>List Help?: [EMAIL PROTECTED]
>
>
>
>--
>--------------------------------------------------------------
>To subscribe: [EMAIL PROTECTED]
>To unsubscribe: [EMAIL PROTECTED]
>List Help?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
