On Thu, 2005-06-30 at 13:15, Heikki Linnakangas wrote:
> On Wed, 29 Jun 2005, Scott Marlowe wrote:
>
> > On Wed, 2005-06-29 at 15:27, Dave Cramer wrote:
> >> I see option A below as the lesser of three evils. Is it reasonable
> >> to believe that people using XA would
> >> know enough to allocate enough connections ?
> >>
> >> Optionally we could have two implementations and choose between A and B
> >
> > If they've used it before with jdbc, yes. It's the way Oracle does it
> > too. Under Jboss you have a two to one ration of backend to frontend
> > connections. I.e. every application connection going through an XA
> > connector requires TWO backend connections.
>
> Do you mean that Oracle opens extra connections behind the scenes? That's
> not what I saw happening. I ran ethereal while running the test case, and
> it showed just one TCP connection and all SQL statements flowing through
> that.
No, our jdbc / jboss connection pooling is doing that. It needs two
connections to the db for every XA transaction.