MuleSoft · JMS Connector

JMS:DESTINATION_NOT_FOUND

Short answer

JMS: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.

VerifiedLast verified

01Error text

MuleSoft error
Error type: JMS:DESTINATION_NOT_FOUND

02Likely causes

  • JMS Connector is not able to find or create the destination.

03How to fix it

  1. Check the destination name the operation receives at run time, and whether it should be a queue or a topic.
  2. Confirm on the broker that the destination exists.
  3. Turn on verbose logging: in log4j2.xml add <AsyncLogger name="org.mule.extensions.jms" level="DEBUG"/> and <AsyncLogger name="org.mule.jms.commons" level="DEBUG"/>. Increase the logging level on the broker side as well.
  4. Handle the failure with an error handler of type JMS:DESTINATION_NOT_FOUND.

04Official documentation

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

The iPaaS Brief

Subscribe to The iPaaS Brief.

The iPaaS newsletter for the people who run integrations. From iPaaS Group.

Free. You finish on theipaasbrief.com and confirm by email.