Is it really thread safety or is this bug caused by a version of jboss that attempts to restart a suspended xid before committing/rollback while the connection/xaresource is in the middle of a second tx?
We used to call start(noflags) end(suspend) //release back to pool, so another tx could get the cx start(resume)//whether or not there was a tx associated!! commit/rollback I'm not sure which jboss versions this is fixed in. thanks david jencks On 2002.09.28 09:46:13 -0400 Igor Fedorenko wrote: > Hi, > > As the subject says -- is XAResource thread-safe or we need to serialize > access to it when accessing the same XAResource instance from multiple > threads? > > I could not find explicit answer to that question in the docs, but did > find that oracle xa implementation is *not* thread safe and SF #614116 > is cause by simultaneous calls to xares.end or xares.start and > xares.rollback from two different threads. > > -- > 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
