Problem

By default, there are no logs present for JMS service related activity (ex: connect, disconnect, errors,etc) in the API Gateway Instance trace.

Only during an exception, there are some class paths mentioned in the stack trace.

Resolution

The logging in the instance trace for MQ can be enabled by adding the corresponding parameters in “/apigateway/system/lib/log4j.properties”. By default, only the parameters for Active MQ are provided in this file.

For IBM MQ, you may add the below lines to the above file and restart Node Manager and API Gateway Instances.

log4j.logger.com.ibm.msg.client.jms=DEBUG

log4j.logger.com.ibm.msg.client.wmq=DEBUG

Additionally, if you have a stack trace with an error from MQ you can see which packages/classes are involved by examining the stack trace and add them to the file.