Maybe I haven't understood the problem correctly. If that is indeed the case, I apologize. But I believe you have I problem where an exception in one of the databases is not rolling back the inserts that happened previously. It is my understanding that that should be the case. I am not sure if you will be able to rollback the inserts from database A unless you have XA enabled on both databases (and you have deployed the bar file with xa enabled).
I noticed that you have two consecutive compute nodes. I wouldn't recommend that. Compute nodes do a tree copy. The tree copy is a copy of a structured object. So it can be expensive (it doesn't just copy bytes).
Maybe I haven't understood the problem correctly. If that is indeed the case, I apologize. But I believe you have I problem where an exception in one of the databases is not rolling back the inserts that happened previously. It is my understanding that that should be the case. I am not sure if you will be able to rollback the inserts from database A unless you have XA enabled on both databases (and you have deployed the bar file with xa enabled).
I noticed that you have two consecutive compute nodes. I wouldn't recommend that. Compute nodes do a tree copy. The tree copy is a copy of a structured object. So it can be expensive (it doesn't just copy bytes).
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
XA is a bit of a 'Dark Art'
It enables proper '2-phase commit' from the broker.
There is plenty of documentation about XA available BUT implementing it will require changes to your infrastructure which if they are done badly could mess it all up.
Also (AFAIK) some databases (I think SQL Server is the culprit here but I might be wrong) do not support XA Coordinated transactions.
You should go bck to first principles and after examining the features that XA provides think long and hard about your requirement and decide if you really, really need to use this feature.
In many cases, I have found that you don't need to use it.
It is an architectural and design issue. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
I am not so sure about SQL Server not supporting XA. I remember that that was the case. Perhaps Data Direct (the company that builds switch files for other databases) might have one for SQL Server also.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum