I suppose that there is no overhead when there is no more than one resource manager in the picture - in which case it should behave completely as if there is no XA at all. I have a configuration now that does not allow registration of XA resources and when turning off the registration of the debug XA Resource it seems there simply is no other XA resource in the picture (but I haven't done much with that setup and simply missed it).
Thanks, Henning Am Freitag, den 24.07.2009, 16:07 -0400 schrieb Harmeet Bedi: > We had done some profiling and did not find profiling bottlenecks due to > commit logic. Single database and default configuration was our setup. > I suspect you question is more theoretical so not sure if this is a useful > answer.. but just sharing our experience. > > Harmeet > > ----- Original Message ----- > From: "Henning" <[email protected]> > To: "user" <[email protected]> > Sent: Friday, July 17, 2009 5:59:45 AM GMT -05:00 US/Canada Eastern > Subject: OfBiz and distributed tx > > While trying to understand OfBiz better, I found that OfBiz relies on > Geronimo's JTA implementation. I have a few questions on that (sorry if > I missed that in the documentation). > > Is OfBiz actually using XAResources and therefore 2-phase-commits? > > And if, is that because of the JMS usage? > > Doesn't that imply a performance penalty that should be avoided if > possible and is there a way to configure OfBiz to handle everything > always in a non-distributed tx? > > Thanks, > Henning > > > >
