MQSeries.net :: View topic

RogerLacroix · Posted: Fri Aug 27, 2021 1:55 pm Post subject:

All,

I have never used Microsoft's BizTalk or MDTC, so I cannot explain what is happening.

I have a customer who is using Capitalware's MQ Message Replication (MQMR) to clone messages going to particular queues. The customer says that BizTalk only reads from queue 'TEST.Q' and they have MQMR setup to clone messages going to 'TEST.Q' and put the copy in queue 'TEST.MQMR.Q'.

They sent me the object definitions for both queues and they are defined as a regular queues and nothing fancy.

They claim when they start the BizTalk service, everything is great but when they stop the BizTalk service, a 'CANCEL' messages shows up in the queue 'TEST.MQMR.Q' which they claim MQMR was doing on its own. MQMR is an API Exit. It only reacts to MQ API calls. It does nothing on its own. They say that BizTalk did not send the message and there is no 'CANCEL' message in the original 'TEST.Q' queue.

I had the customer enable debug tracing in MQMR and the trace shows that MQMR is being invoked by the queue manager for an MQPUT API call with that 'CANCEL' message.

While the customer sees the evidence in the MQMR log file, they are still saying that BizTalk did not put the 'CANCEL' message to queue 'TEST.Q'.

The other piece to the puzzle is that BizTalk Is using MDTC transaction manager.

So, I need some help from our MQ Windows geeks. Has anyone seen this behavior before? Could it be that BizTalk backed out the 'CANCEL' message and because MDTC is handling the transaction, MQ did not back out the cloned message?

Any info or pointers to what is going on would be greatly appreciated.

Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter