MuleSoft · IBM MQ Connector
IBM-MQ:CONNECTIVITY
Short answer
IBM-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.
VerifiedLast verified
01Error text
Error type: IBM-MQ:CONNECTIVITY02Likely causes
- The connection is no longer valid. The connection is disposed of.
- When the On New Message listener shares a configuration with Publish or Consume, a connection failure in those operations can hang the listener.
03How to fix it
- Check that the queue manager is running and reachable from the Mule app.
- Use a dedicated configuration for the On New Message listener.
- Configure a reconnection strategy on the IBM MQ configuration.
- 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:CONNECTIVITY.
04Official documentation
→Related errors
- IBM-MQ:CONSUMINGIBM-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.
- IBM-MQ:DESTINATION_NOT_FOUNDIBM-MQ:DESTINATION_NOT_FOUND means IBM MQ Connector could not find or create the destination. Check the queue or topic name against what exists on the queue manager.
- JMS:CONNECTIVITYJMS:CONNECTIVITY means the JMS connection is no longer valid, and the connector disposes of it. Check the broker and configure a reconnection strategy so the app reconnects by itself.
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