Ha ha ha. Found it. Once I opened the right file, Invocation.java, it was totally obvious. The constructor for Invocation was missing call to setTransaction, so the existing tx was ignored.
I checked the fix in. -dain > -----Original Message----- > From: Dain Sundstrom [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, December 26, 2001 8:22 PM > To: 'marc fleury'; [EMAIL PROTECTED] > Subject: RE: RE: [JBoss-dev] Screwed up TxInterceptorCMT > > > Just got back from dinner at my parents. I'll start looking > at this now. > > -dain > > -----Original Message----- > From: marc fleury [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, December 26, 2001 3:54 PM > To: [EMAIL PROTECTED] > Subject: Re: RE: [JBoss-dev] Screwed up TxInterceptorCMT > > > > > let me dig 5 minutes and I will go back to deployers > > ok here is what I have so far, > > the tm should be initialized properly in the BLCI, > > put a trace in the invoke() call and see that > > 1- you have tm stop if you don't > 2- the tx is there stop if it is not > 3- that the Invocation that is created is not transformed in a > MarshalledInvocation due to classloader problems in your > packaging (look at > your logs) > > let me know I am going back to my work > > > ______________________________________________________________________ > View this jboss-dev thread in the online forums: > http://jboss.org/forums/thread.jsp?forum=66&thread=6276 > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
