Posted: Tue Aug 27, 2002 1:51 am Post subject: MQBegin with MQ as the XA coordinator
Apprentice
Joined: 04 Feb 2002 Posts: 26
When sending an MQBegin to the QMGR it seems that the QMGR attempts to connect / coordinate with the Oracle DB's in the mq.ini file, evan if the specific transaction will not involve all of them.
This is a problem since some of the entries in the mq.ini are not always available.
I read in the documentation that "the queue manager first asks each participating database manager whether it is prepared to commit its updates" but it seems it does something similar to this at the MQBegin.
****
Is there any way to instruct the QMGR NOT to try all the coordinated resources in the mq.ini ?
****
The qmgr will always contact all DBs listed in the qm.ini for an
xa_open call (ie the first MQBEGIN an app makes). Whether or not it then goes on to issue xa_start for subsequent MQBEGINs for that application depends on whether the DB uses static or dynamic XA registration.
If you have the December 2001 issue of Xephon's MQ Update magazine you will find a technique for avoiding the xa_open on all DBs, but it requires custom coding on your part to match your particular environment.
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