MuleSoft · IBM MQ Connector
IBM-MQ:CONSUMING
Short answer
IBM-MQ:CONSUMING means an error occurred while consuming messages, and it can simply mean no message was pending. If the app has stopped consuming, look for a backlog of unacknowledged messages.
VerifiedLast verified
01Error text
Error type: IBM-MQ:CONSUMING02Likely causes
- An error occurred while consuming messages from WMQ. This error might relate to the absence of a pending message.
- A large number of unacknowledged messages can make the consumer stop.
03How to fix it
- Check the depth of unacknowledged messages on the broker side and review the application logic.
- Be sure that every message is acknowledged or the session recovers.
- Turn on verbose logging: in
log4j2.xmladd<AsyncLogger name="com.mulesoft.connectors.ibmmq" level="DEBUG"/>and<AsyncLogger name="org.mule.jms.commons" level="DEBUG"/>. Increase the logging level on the server side as well. - Handle the failure with an error handler of type
IBM-MQ:CONSUMING.
04Official documentation
→Related errors
- IBM-MQ:CONNECTIVITYIBM-MQ:CONNECTIVITY means the IBM MQ connection is no longer valid, and the connector disposes of it. Check the queue manager, configure reconnection, and give the listener its own configuration so a failed Publish or Consume cannot hang it.
- IBM-MQ:TIMEOUTIBM-MQ:TIMEOUT means the timeout for the requested IBM MQ operation was exceeded. Check why no message or reply arrived in time before raising the timeout.
- JMS:CONSUMINGJMS:CONSUMING means an error occurred while consuming messages, and it can simply mean no message was pending. If consumption has stopped altogether, look for a backlog of unacknowledged messages on the broker.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for MuleSoft work:Open MuleSoft jobsMuleSoft rates and salariesHire a senior MuleSoft developer