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
Error type: JMS:DESTINATION_NOT_FOUND02Likely causes
- JMS Connector is not able to find or create the destination.
03How to fix it
- Check the destination name the operation receives at run time, and whether it should be a queue or a topic.
- Confirm on the broker that the destination exists.
- Turn on verbose logging: in
log4j2.xmladd<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. - Handle the failure with an error handler of type
JMS:DESTINATION_NOT_FOUND.
04Official documentation
→Related errors
- JMS:PUBLISHINGJMS:PUBLISHING means there was an error while publishing to the target queue or topic. Check the destination and the broker, then read the underlying cause with verbose logging on.
- JMS:SECURITYJMS:SECURITY means the JMS operation failed because of a security-related error. Check the credentials in the JMS connection and what that user is allowed to do on the broker.
- 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