> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of David
> Jencks
> Sent: Wednesday, June 27, 2001 9:44 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-dev] High load...
>
>
> Hi,
> On 2001.06.26 23:30:32 -0400 marc fleury wrote:
> > |2 entity beans. 2 connection pools(but same database), each connection
> > pool
> > |is configured to use a certain JDBC isolation level. Entity 1 is attach
> > to
> > |pool 1, Entity 2 is attached to pool 2.
> >
> > yuck...
> >
> > I still don't have a clear answer to
> >
> > what we do = (does a jdbc connection support setting isolations level on
> > the
> > fly)? we use one pool and the container sets levels : we are stuck with
> > many
> > pools
> >
> Well, a jdbc connection certainly supports setting isolation levels. I
> think when you can do it depends on the db. I think generally it only
> makes sense to change when there is no uncommitted work (between
> transactions), even though apparently some dbs (someone said informix) may
> let you change within a transaction.
>
> > marcf
> >
> > PS: of course many pools works but yuck!
> >
> > |
> > |1. Start JBoss transaction
> > |2. Access Entity1. A connection is grabbed from pool 1,
> > |connection1.setIsolation(blah blah),
> > |3. access entity2. A connection is created from pool 2,
> > |connection2.setIsolation(blah blah)
> > |4. End JBoss transaction. commit is called on connection 1 and
> > connection
> > |2.
> > |
> > |This should work, shouldn't it?
> > |
>
> Well, maybe. To make this work, you require true xa capable drivers, and
> you need to use real 2pc, not the fake stuff from jbosspool wrappers. The
> wrapped drivers will give you 2 independent conncurrent transactions.
>
I don't know about you, but I'm happy with the fake XA that the jbosspool
wrappers provide. Shouldn't it work 99.999% of the time?
Bill
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
