XA enabled resources
XA support extends transaction support as it allows WAS to coordinate a transaction over many back end resources, committing the results to those resources only when all the work in the transaction has been completed.
JMS Provider: WebSphere JMS and WebSphere MQ JMS Component: QCF and TCF Applies to specific messaging topologies: Yes Requires specific usage of JMS in application: No Location of setting: Resources | WebSphere MQ JMS Provider | WebSphere MQ Queue Connection Factories | Your_QCF | Enable XA checkbox 2phase commit can only operate with XA enabled resources and this setting specifies this.
By default, XA support is enabled when creating a QCF or TCF. With XA enabled more work has to be done to complete the transaction. It is an expensive overhead if there is no use of two phase commit in your application and so should be disabled. Be aware that disabling XA support will only work if your application does not use this resource as part of a global transaction. Turning this off does not change behavior of a transaction, if XA enabled is set to false and the application tries to enlist more than one resource in the transaction, then an exception will be thrown.
If your application does need to use an XA enabled QCF or TCF then establish whether it is needed for all interactions with the messaging system. If it is only needed for a small section of the application requests then it is recommended that two connection factory objects are created, one with XA enabled and one without. This should then make the parts of the application that do not need XA run faster.
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.