MuleSoft · IBM MQ Connector
IBM-MQ:DESTINATION_NOT_FOUND
Short answer
IBM-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.
VerifiedLast verified
01Error text
Error type: IBM-MQ:DESTINATION_NOT_FOUND02Likely causes
- IBM MQ Connector is not able to find or create the destination.
03How to fix it
- Check the destination name the operation receives at run time.
- Confirm on the queue manager that the destination exists.
- 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:DESTINATION_NOT_FOUND.
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.
- JMS:DESTINATION_NOT_FOUNDJMS:DESTINATION_NOT_FOUND means JMS Connector could not find or create the queue or topic. Check the destination name and that the connecting user is allowed to use or create it 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