Loading

How to enable debug logging at IBM MQ Classes for JMS driver level

Publiceringsdatum: Jul 24, 2025
Uppgift

GOAL

To enable tracing (debug logging) at WMQ / IBM MQ driver level to troubleshoot MQ connection or operation related issues. 
Steg
Add JVM properties provided in the below section during startup of Mule server to enable WMQ / IBM MQ client level tracing. Refer to How can I set Mule and Java system properties at startup?

MQ version v6

This method is still available in V7, but it is deprecated. It is suggested to use the new JMS trace facilities introduced in V7. See the next section. 
MQJMS_TRACE_LEVEL=base
MQJMS_TRACE_DIR=/tmp
MQ version v7 and above 
com.ibm.msg.client.commonservices.trace.status=ON
com.ibm.msg.client.commonservices.trace.level=8
com.ibm.msg.client.commonservices.trace.outputName=/tmp/mule_mqjms_%PID%.log
To restrict maximum trace file size 250MB and no of trace files to 2:
com.ibm.msg.client.commonservices.trace.limit=262144000
com.ibm.msg.client.commonservices.trace.count=2
Other optional parameters to experiment: https://www.ibm.com/docs/en/ibm-mq/9.0?topic=file-java-standard-environment-trace-stanza

Connector level tracing

The above procedure enables tracing at the IBM driver level. Additionally, you should enable verbose / debug logging at the WMQ / IBM MQ connector level. Refer to How to enable verbose / debug logging for the WMQ / IBM MQ connector.

REFERENCE

For details on available properties and values
Tracing IBM WebSphere MQ classes for JMS applications
Generating IBM MQ traces
Knowledge-artikelnummer

001114764

 
Laddar
Salesforce Help | Article