Morning
An on-prem .NET application puts persistent messages into a remote queue (QR1) from an IBM MQ 9.2.11 queue manager on AWS (QM1) via amqmqnet.dll version 1.0.0.3. The QR1 queue directs the messages to the QM2 transmission queue on a host in AWS. Queue manager QM1 has a dedicated link with queue manager QM2 (geographically distinct infrastructures).
PROBLEM:
Dedicated links failed and the .NET application user reported that a message flowing from the application to QM1 had been committed to the application and had not been registered in the QM2 queue manager after the link was restored.
Troubleshooting:
1 - We analyzed the transmission queue and DLQ and the message was not there.
2 - We dumped messages from the log and the message was also not persisted.
3 - The QM1, Client MQ and application logs did not present any failure at the time described by the application user.
4 - We investigate the network traffic, via wireshark, and at the moment informed by the user, a packet is seen traveling with MQPUT and the return of a MQPUT_REPLY.
What other analysis can I do to find out what is happening?
I can't understand how a link failure would affect this post, they are different channels and different addresses
Thanks
Jales, Jorge
------------------------------
JORGE JALES
BTG PACTUAL
------------------------------