Debugging messaging applications with IBM MQ

I've recently published my second debugging messaging applications tutorial, which is Open Telemetry (OTel) centric. The first tutorial was about using the IBM MQ console. In total, we now have five related articles in the "Debugging IBM MQ messaging applications" series.

In addition to this content on IBM Developer, we have several troubleshooting blogs on our IBM MQ Community blog.

Some are OTel specific, as it's a hot topic! Our new tutorial will give you a good introduction to OTel and messaging applications.

• "More easily understand where your messages are going with OpenTelemetry trace support in IBM MQ for z/OS"

• "OpenTelemetry Tracing service on the IBM MQ Appliance"

Some relate to metrics:

• "Introduction to the IBM MQ Performance Tool (mqperfck)"

Some are mini-articles in their own right:

• Special considerations when using JMS Request-Response applications in a Uniform Cluster. You can learn more about Uniform clustering in IBM MQ in this series by Simone Jain.

Some relate to containers:

• "Testing IBM MQ with Testcontainers in Spring Boot — Made Easy"

• "Building a customised IBM MQ Container on WSL 2"

Some are just snippets of wisdom:

• "Why do the MQ classes for Java, classes for JMS and classes for Jakarta Messaging need org.json.jar on their CLASSPATH?"

• "Why is WebSphere Application Server (WAS) connecting to MQ using the user that started it rather than the user in the authentication alias?"

• "Why are my applications seeing MQRC 2035 errors after upgrading to WebSphere Application Server 9.0.5.20 or later?"

• "Understanding and resolving MQRC_FORMAT_ERROR when using amqsget with MQTT messages"

These blogs in conjunction with our troubleshooting tutorials provide a toolset that will help you identifying the cause of any issues you might see.