Yeah, but not at the moment, I am way busy right now. --jason
> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:jboss- > [EMAIL PROTECTED]] On Behalf Of Larry Sanderson > Sent: Thursday, August 08, 2002 2:19 PM > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-dev] [ jboss-Bugs-590816 ] XAProto Errors on closed > XAResources > > Only JBossMQ and Informix XA. Not SwiftMQ yet. Do you have a setup where > you can test this? > > -Larry > > ----- Original Message ----- > From: "Jason Dillon" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, August 08, 2002 2:07 PM > Subject: RE: [JBoss-dev] [ jboss-Bugs-590816 ] XAProto Errors on closed > XAResources > > > > Have these patchs been used and verfified with JBossMQ and SwiftMQ? > > > > --jason > > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] [mailto:jboss- > > > [EMAIL PROTECTED]] On Behalf Of Larry Sandereson > > > Sent: Thursday, August 08, 2002 2:03 PM > > > To: [EMAIL PROTECTED] > > > Subject: Re: [JBoss-dev] [ jboss-Bugs-590816 ] XAProto Errors on > > closed > > > XAResources > > > > > > I think I may have tracked down the SwiftMQ bug... let me know if this > > > sounds right. > > > > > > SwiftMQ doesn't support start(suspend), so they return false for all > > calls > > > to isSameRM(). This should cause all connections being enlisted to be > > > given > > > a unique xid (with different branch qualifiers). I think this is > > > compliant > > > with the JTA and XA specs. > > > > > > In enlistResource (TransactionImpl:535), a check is made to see if > > this RM > > > is already enlisted (call to findResource). But, this check uses an > > > equality test. If you are enlisting a connection that was previously > > > closed > > > in the same transcation scope, then this will find the old resource, > > and > > > attempt to re-enlist with a TMJOIN, which on SwiftMQ yields an > > XAException > > > (PROTO?). > > > > > > Basically, we can't assume that (resource1 == resource2) implies > > > (resource1.isSameRM(resource2)). > > > > > > The problem now is that the TM must be able to enlist the same > > resource > > > multiple times with different branch-ids, and then figure out which > > xid to > > > use on the next call to delist. > > > > > > I have attached a patch (one for JBoss 3.1 one for JBoss 3.0) that I > > think > > > fixes the problem. Please let me know what you think. > > > > > > -Larry > > > > > > > > ------------------------------------------------------- > > 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 ------------------------------------------------------- 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
