Are your XA Resources slowing you down?
ThomasBien 060001PQVD Visits (4312)
Global coordination is very useful in WebSphere Message Broker (WMB) when needing to ensure that all parts of a transaction complete together. WebSphere MQ does a great job of acting as a transaction manager for WMB. However, when configuring XA, it is essential that we coordinate only the resources we need.
When an XA transaction is committed, your transaction resource manager will go down its list of resources and commit each of them. While each resource is informed, a small delay is incurred. In situations where there are a large number of resources, this could very quickly add up to a large delay, which may negatively impact processing.
If you are seeing poor performance with your XA enabled message flows, take a second to look at your WebSphere MQ Queue Manager's qm.ini file and review your list of XA stanzas. If you have several resources configured, you may want to investigate some changes:
You may find a significant improvement to your transaction speeds by removing outdated resource stanzas, or even moving to a queue manager with fewer external resource commitments. For one broker, we found that we saved 5 seconds - per transaction!