All geek questions in one place

How to check which point is causing the MQ problem?

I use MQ to send / receive messages between my system and another system. Once I discovered that there is no response message in the response queue, and the other system has already sent a response message to the response queue (check from the log). So, how to check which point is the cause of the problem, how to prove that the message does not arrive in my reply queue.

In addition, when a message arrives in my queue, it will be written to the log file.

+3
source share
1 answer

You can view it in real time using the QStats interface. MO71 SupportPac is a desktop client that can be configured to connect in the same way as WebSphere MQ Explorer. One of the options he has is queue statistics. Each time you look at the statistics of the queues, WMQ resets them to zero. So the procedure is as follows:

  • Launch MO71 and view the queues.
  • Filter in the single queue of interest.
  • Look at the queue statistics a couple of times.
  • You will see that they reset are zero.
  • Now run your test.
  • Review the queue statistics again.

If the remote program does send a message, you will see that the queue now shows one or more PUT messages.

GET , , GET PUT.

GET PUT , .

, . SupportPac MA0W, API PID - . , , (.. ), . MA0W , QMgr , .

0

Source: https://habr.com/ru/post/1739075/

More articles:


All Articles