MQSeries.net :: View topic

shashivarungupta · Posted: Sun Feb 22, 2015 3:02 pm Post subject: XA Transaction Setting, Decision?

Hi,

I know this topic has been touched so many times in this forum through one or many different questions, but I would like to concentrate on the objective to have Globally Coordinated Transaction and actually 'When?' and 'When we should not have it?'.

[Here, I am talking about the distributed platform only and ODBC connections. Say, a configured Broker is of v8.]

As we know that message flow transactions are managed by broker, by default and commit/rollback depends on the success/failure of main message flow and its Input node Transaction Mode Settings. (Unless different Transaction Mode settings are applied to different nodes down the message flow.)

So, we should be having XA Transaction Configuration ONLY when there are different SYSTEM DSN used in a main & its sub flows to interact with same/different databases, over a sync point?
Or there are other effective reasons for having XA Transaction ?

Since XA Transaction configuration brings up additional set of operations for administrator and the performance overhead for deployed broker application, would it be suffice to say that XA transaction should not be used when performance is critical?

Thanks.
_________________
*Life will beat you down, you need to decide to fight back or leave it.