If you want to use transactions distributed across multiple jboss servers you currently have to use the Tyrex dtm plugin. I don't know to what extent it has actually been tested with the various 3.x/4.0 versions of jboss.
In jboss 4, a lot of what's needed for distributed transactions in the jboss tm is implemented in the transaction inflow contracts from jca 1.5. We still need a connector of some sort to get the calls from one jboss instance to the other. Also the jboss tm does no logging currently so won't provide any recovery support. As to whether this is a cornerstone of j2ee -- I don't have a lot of real world experience with this but I would expect you would usually get much better performance and resource utilization by keeping each unit of work in one vm and distributing the work through clustering (or just running lots of servers in parallel) and partitioning the work sequentially through MOM. So, althought the spec pushes it extensively, it may not be a really practical design for real systems. What do you think? I think the effect of removing the client session bean tx interceptor is that jboss doesn't try to propagate a transaction between servers, and your work is not done in a single transaction. Thanks david jencks On 2002.09.03 10:52:14 -0400 Josh Davis wrote: > I'm using JBoss 3.0. The interesting thing is, is that in the > standardjboss.xml file I found the container configuration for the > standard > stateless session beans and I commented out the transaction intercepter > in > the client. When I restarted my distributed calls work fine. > > Here is my guess as to what is happening. JBoss starts a transaction > when > the client session bean is called on. When the client session bean tries > to > make a distributed call to the other jboss instance it tries to pass on > the > transaction information as well. In this case none of the transaction > code > is serializable. David Jencks makes mention of this in a distributed > transaction email thread. This makes sense as to why it is happening. > > The main problem that I'm having is how are people getting this to work > by > leaving the transaction interceptor in place. My assumption is nobody > has > this working with version 3.0. Also what are the implications of leaving > > the transaction interceptor commented out? > > Shouldn't you theoretically be able to call any bean on any jboss > instance > in a distributed environment? Isn't this what the J2EE architecture is > all > about? > > Josh Davis > > >-----Original Message----- > >From: Sacha Labourey [mailto:[EMAIL PROTECTED]] > >Sent: Saturday, August 31, 2002 1:56 AM > >To: [EMAIL PROTECTED] > >Subject: RE: [JBoss-user] Is anyone able to use two jboss's on different > >machines? > > > > > >Hello, > > > >Can you please provide us with: > > - the version (3.0.2, 3.2beta, HEAD, etc.) > > - the client code and any config file > > - the stack trace > > > > > >Cheers, > > > > Sacha > > > > > -----Message d'origine----- > > > De : [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED]]De la part de Josh > Davis > > > Envoy� : vendredi, 30 ao�t 2002 19:47 > > > � : [EMAIL PROTECTED] > > > Objet : RE: [JBoss-user] Is anyone able to use two jboss's on > different > > > machines? > > > > > > > > > I can see the other machine because the jndi call successfully > > > completes the > > > initial lookup of the home interface. The problem arises when the > > > home.create() method is called from the client jboss instance. I get > a > > > NotSerializableException on a TransactionImpl class. Why is a > > > TransactionImpl class even involved in my call to the other jboss > > > instance? > > > The home.create() should just return the remote stub to me. Do I > have > >to > > > configure something so the transaction interceptor isn't being > > > used. Using > > > tyrex produces the same problem. > > > > > > Josh (java guru) Davis > > > > > > >-----Original Message----- > > > >From: Emerson Cargnin - SICREDI Servi�os > > > >[mailto:[EMAIL PROTECTED]] > > > >Sent: Friday, August 30, 2002 11:16 AM > > > >To: [EMAIL PROTECTED] > > > >Subject: Re: [JBoss-user] Is anyone able to use two jboss's on > >different > > > >machines? > > > > > > > > > > > >you have to have a jndi.properties in the classpath to allow > > > jboss to see > > > >the other host. > > > > > > > >Josh Davis wrote: > > > > > Does anyone have JBoss 3.0 running on two different machines > > > with ejb > > > > >lookups working correctly between them? I'm not talking > > > clustering > here. > > > > I want to know if anyone can successfully do a lookup from a > > >session > > > >bean to a session bean on two different machines running jboss. > > > > > > Lookups work fine from an ear file to another ear file > > > deployed in the > > > > > same jboss instance on the same machine, but fails > > > distributedly. Have > > > > > I configured something wrong? > > > > > > Josh (java guru) Davis > > > > > > > > > > > _________________________________________________________________ > > > > > MSN Photos is the easiest way to share and print your photos: > > > > >http://photos.msn.com/support/worldwide.aspx > > > > > > > > ------------------------------------------------------- > > > > > This sf.net email is sponsored by: OSDN - Tired of that same old > > > > > cell phone? Get a new here for FREE! > > > > > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > > > > > _______________________________________________ > > > > > JBoss-user mailing list > > > > > [EMAIL PROTECTED] > > > > > https://lists.sourceforge.net/lists/listinfo/jboss-user > > > > > > > > > > > > > > > > >-- > > > >Emerson Cargnin - MSA > > > >SICREDI - Tel : 3358-4860 > > > > > > > > > > > > > > > >------------------------------------------------------- > > > >This sf.net email is sponsored by: OSDN - Tired of that same old > > > >cell phone? Get a new here for FREE! > > > >https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > > > >_______________________________________________ > > > >JBoss-user mailing list > > > >[EMAIL PROTECTED] > > > >https://lists.sourceforge.net/lists/listinfo/jboss-user > > > > > > > > > > _________________________________________________________________ > > > MSN Photos is the easiest way to share and print your photos: > > > http://photos.msn.com/support/worldwide.aspx > > > > > > > > > > > > ------------------------------------------------------- > > > This sf.net email is sponsored by: OSDN - Tired of that same old > > > cell phone? Get a new here for FREE! > > > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > > > _______________________________________________ > > > JBoss-user mailing list > > > [EMAIL PROTECTED] > > > https://lists.sourceforge.net/lists/listinfo/jboss-user > > > > > > > > > > >------------------------------------------------------- > >This sf.net email is sponsored by: OSDN - Tired of that same old > >cell phone? Get a new here for FREE! > >https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > >_______________________________________________ > >JBoss-user mailing list > >[EMAIL PROTECTED] > >https://lists.sourceforge.net/lists/listinfo/jboss-user > > > > > _________________________________________________________________ > Chat with friends online, try MSN Messenger: http://messenger.msn.com > > > > ------------------------------------------------------- > This sf.net email is sponsored by: OSDN - Tired of that same old > cell phone? Get a new here for FREE! > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > > ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
