Not finalized yet. Public review of the first public draft ended June 16, I hope they take the time to read my comments and incorporate them... unlike te jdo guys. There are a bunch of cool things. The tx inflow contract should make adding the "d" to our tm pretty easy.
david On 2002.06.24 15:52:21 -0400 Jason Dillon wrote: > Do you know when this spec will finalize... or if it has already? > > --jason > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:jboss- > > [EMAIL PROTECTED]] On Behalf Of David Jencks > > Sent: Wednesday, June 19, 2002 7:29 PM > > To: [EMAIL PROTECTED] > > Subject: Re: [JBoss-dev] SwiftMQ JMS RA problems closer to > resolution... > > > > Possibly Andreas Muller is not aquainted with jca 1.5, perhaps the > main > > focus of which is to enable pluggable jms implementations through jca, > > primarily by supporting inbound transactional messaging through jca > (the > > sticky part of the current jms ra adapter). I think the jca group > thinks > > using jca for outbound messaging is a no brainer. > > > > In other words I disagree with his assessment of the appropriateness > of > > our > > adapter. > > > > However, if we are sending TMJOIN to an XAResource that identifies > itself > > as being a different rm as the branch we are joining, that looks like > a > > bug > > in our tm. I'll take a look. > > > > david jencks > > > > On 2002.06.19 15:20:23 -0400 Jason Dillon wrote: > > > I now know why SwiftMQ does not like the JBoss JMS RA. It does not > > > accept TMJOIN as a valid flag to XAResource.start(). Here is the > > > explaination from Andreas Mueller as to why (from the SwiftMQ > forums): > > > > > > > > > > > > <snip> > > > > > > Every XA session in SwiftMQ returns a distinct XAResource. It > returns > > > false if XAResource.isSameRM is called. Therefore a TMJOIN isn't > > > possible, rather it is forced with XAResource.isSameRM to handle > each of > > > our XAResource as a distinct XAResource to be enlisted at the JTA > tx. So > > > what the JMS RA does is wrong. It must handle our XAResource as a > > > distinct XAResource to start with TMNOFLAGS. > > > > > > TMRESUME can be called on our XAResource if the Xid was suspended > > > before. > > > > > > Except the MDB/XA handling which I have forced to implement that way > I > > > find the JMS RA of JBoss quite terrible. JCA 1.0 isn't approriate > for > > > JMS. A much better solution would be to write a clean proxy that > does > > > the JMS XA handling for outbound messaging behind the scene. All > other > > > app servers are doing it that way. Only JBoss uses this strange RA > > > stuff. > > > > > > </snip> > > > > > > > > > > > > But the problem still remains unsolved. I think that I might be > able to > > > get around this on the app side. but I am not sure exactly what I > need > > > to do to force the flags to XAResource.start() to be TMNOFLAGS. > Does > > > anyone know? > > > > > > > > > > > > Also, is there a way to fix the JMS RA as it is so TMJOIN would > never be > > > used? > > > > > > > > > > > > And finally, if it is a good idea to implement the XA proxy thingy > > > instead of the JCA fluff, any ideas on how to do that? I am slowly > > > becoming forced to learn about all this XA madness, though I have > been > > > resisting for several months now. > > > > > > > > > > > > Andreas suggests that others use this proxy thingy, does anyone know > of > > > an LGPL version that I could look at? > > > > > > > > > > > > --jason > > > > > > > > > <html> > > > > > > <head> > > > <META HTTP-EQUIV="Content-Type" CONTENT="text/html; > charset=us-ascii"> > > > > > > > > > <meta name=Generator content="Microsoft Word 10 (filtered)"> > > > > > > <style> > > > <!-- > > > /* Font Definitions */ > > > @font-face > > > {font-family:Verdana; > > > panose-1:2 11 6 4 3 5 4 4 2 4;} > > > /* Style Definitions */ > > > p.MsoNormal, li.MsoNormal, div.MsoNormal > > > {margin:0in; > > > margin-bottom:.0001pt; > > > font-size:12.0pt; > > > font-family:"Times New Roman";} > > > a:link, span.MsoHyperlink > > > {color:blue; > > > text-decoration:underline;} > > > a:visited, span.MsoHyperlinkFollowed > > > {color:purple; > > > text-decoration:underline;} > > > span.EmailStyle17 > > > {font-family:Arial; > > > color:windowtext;} > > > @page Section1 > > > {size:8.5in 11.0in; > > > margin:1.0in 1.25in 1.0in 1.25in;} > > > div.Section1 > > > {page:Section1;} > > > --> > > > </style> > > > > > > </head> > > > > > > <body lang=EN-US link=blue vlink=purple> > > > > > > <div class=Section1> > > > > > > <p class=MsoNormal><font size=2 face=Arial><span style='font- > > size:10.0pt; > > > font-family:Arial'>I now know why SwiftMQ does not like the JBoss > JMS > > > RA. > > > It does not accept TMJOIN as a valid flag to > XAResource.start(). > > > Here is > > > the explaination from Andreas Mueller as to why (from the SwiftMQ > > > forums):</span></font></p> > > > > > > <p class=MsoNormal><font size=2 face=Arial><span style='font- > > size:10.0pt; > > > font-family:Arial'> </span></font></p> > > > > > > <p class=MsoNormal><font size=2 face=Arial><span style='font- > > size:10.0pt; > > > font-family:Arial'><snip></span></font></p> > > > > > > <p class=MsoNormal><font size=2 face=Verdana><span > > > style='font-size:10.0pt; > > > font-family:Verdana'>Every XA session in SwiftMQ returns a distinct > > > XAResource. > > > It returns false if XAResource.isSameRM is called. Therefore a > TMJOIN > > > isn't > > > possible, rather it is forced with XAResource.isSameRM to handle > each of > > > our XAResource > > > as a distinct XAResource to be enlisted at the JTA tx. So what the > JMS > > RA > > > does > > > is wrong. It must handle our XAResource as a distinct XAResource to > > start > > > with > > > TMNOFLAGS.<br> > > > <br> > > > TMRESUME can be called on our XAResource if the Xid was suspended > > > before.<br> > > > <br> > > > Except the MDB/XA handling which I have forced to implement that way > I > > > find the > > > JMS RA of JBoss quite terrible. JCA 1.0 isn't approriate for JMS. A > much > > > better > > > solution would be to write a clean proxy that does the JMS XA > handling > > > for > > > outbound messaging behind the scene. All other app servers are doing > it > > > that > > > way. Only JBoss uses this strange RA stuff.</span></font></p> > > > > > > <p class=MsoNormal><font size=2 face=Verdana><span > > > style='font-size:10.0pt; > > > font-family:Verdana'></snip></span></font></p> > > > > > > <p class=MsoNormal><font size=2 face=Verdana><span > > > style='font-size:10.0pt; > > > font-family:Verdana'> </span></font></p> > > > > > > <p class=MsoNormal><font size=2 face=Verdana><span > > > style='font-size:10.0pt; > > > font-family:Verdana'>But the problem still remains unsolved. I > > > think that > > > I might be able to get around this on the app side… but I am > not > > > sure > > > exactly what I need to do to force the flags to XAResource.start() > to be > > > TMNOFLAGS. Does anyone know?</span></font></p> > > > > > > <p class=MsoNormal><font size=2 face=Verdana><span > > > style='font-size:10.0pt; > > > font-family:Verdana'> </span></font></p> > > > > > > <p class=MsoNormal><font size=2 face=Verdana><span > > > style='font-size:10.0pt; > > > font-family:Verdana'>Also, is there a way to fix the JMS RA as it is > so > > > TMJOIN > > > would never be used?</span></font></p> > > > > > > <p class=MsoNormal><font size=2 face=Verdana><span > > > style='font-size:10.0pt; > > > font-family:Verdana'> </span></font></p> > > > > > > <p class=MsoNormal><font size=2 face=Verdana><span > > > style='font-size:10.0pt; > > > font-family:Verdana'>And finally, if it is a good idea to implement > the > > > XA proxy > > > thingy instead of the JCA fluff, any ideas on how to do that? > I am > > > slowly > > > becoming forced to learn about all this XA madness, though I have > been > > > resisting > > > for several months now.</span></font></p> > > > > > > <p class=MsoNormal><font size=2 face=Verdana><span > > > style='font-size:10.0pt; > > > font-family:Verdana'> </span></font></p> > > > > > > <p class=MsoNormal><font size=2 face=Verdana><span > > > style='font-size:10.0pt; > > > font-family:Verdana'>Andreas suggests that others use this proxy > thingy, > > > does > > > anyone know of an LGPL version that I could look > at?</span></font></p> > > > > > > <p class=MsoNormal><font size=2 face=Verdana><span > > > style='font-size:10.0pt; > > > font-family:Verdana'> </span></font></p> > > > > > > <p class=MsoNormal><font size=2 face=Verdana><span > > > style='font-size:10.0pt; > > > font-family:Verdana'>--jason</span></font></p> > > > > > > </div> > > > > > > </body> > > > > > > </html> > > > > > > > > > ------------------------------------------------------- > > Bringing you mounds of caffeinated joy > > >>> http://thinkgeek.com/sf <<< > > > > _______________________________________________ > > Jboss-development mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > ------------------------------------------------------- > Sponsored by: > ThinkGeek at http://www.ThinkGeek.com/ > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > ------------------------------------------------------- Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
