yes, if you take a look at the code, before the switch statement that distinguishes the cases between the different transaction attributes, we start by a tx.suspend() and, a few lines after, a tx.resume() if it was a REQUIRES tag for example, etc.
> -----Message d'origine----- > De : [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]De la part de marc > fleury > Envoye : lundi, 27 janvier 2003 16:52 > A : [EMAIL PROTECTED]; 'Stefan Reich' > Objet : RE: [JBoss-dev] RE: how's ecperf going? > > > > > * TxInterceptorCMP suspends and resumes a transaction in all cases, > > > sometimes even twice. This can be very expensive, especially with > > > global transactions. > > > > > > > ?? Can you point this out? > > for the nth time we are having this discussion. > > NO, the 'suspend/resume' is NOT A LIFECYCLE EVEN ON THE TRANSACTION. > That says that there is no distribution of that event. S/R just says > that we DIS-ASSOCIATE the thread from the transaction and that's it. If > a TM implements notifications of this, it is A BUG. > > marcf > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
