This is in HEAD and 3.2. Both Local and XAConnectionManagers are wrappers around TxConnectionManager. In XA and TxConnectionManager you can set TrackConnectionByTx to eliminate all intermediate end(suspend) and start(resume) calls. Also, all work on one tx will go through one connection.
A side effect of this (currently at least) is that a connection will only be usable by one tx until the tx commits. david jencks On 2002.09.30 18:41:47 -0400 Igor Fedorenko wrote: > Hi, > > I rememeber there was a discussion about keeping jdbc xa connection > allocated for a transaction until the transaction ends. Is it > implemented? > > -- > Igor Fedorenko > Think smart. Think automated. Think Dynamics. > www.thinkdynamics.com > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
