IBM Websphere MQ Latency 用于存储持久消息 Java 客户端

Question

In Websphere9 Console for "Queues", we have "Default messaging provider" and "WebSphere MQ messaging provider". One of our Q has been created with "Default messaging provider". Now we observe some performance issue with this Q on Latency area. When we are having high load in application via this MQ, Latency comes and data is not getting painted in UI. This is an intermittent issue, but we want to know is it related to latency or some other MQ tuning will resolve or not? what kind of trace we can enable for "Default messaging provider" and other other tuning to resolve latency?

17-May-2021

WebSphere Console to get Depth Set and used Depth ["Default messaging provider"]

--current depth set Queue["Default messaging provider"] ---

Security > Bus Security > Bus > Messaging engines > cluster1.001- Bus > Queue points > *****Queue@cluster1.001-*Bus>>"High message threshold "

--current Queue["Default messaging provider"] depth on peak time---

Security > Bus Security > Bus > Messaging engines > cluster1.001- Bus > Queue points

Answer 1

Latency can be caused by applications being too slow to process the work. This in turn can be caused by applications taking too long to process the transaction eg quick MQ request, and long SQL request followed by commit. Or it could be caused by not enough threads processing the work. As a first step increase the number of transactions processing the work.