MuleSoft · JMS Connector
JMS:SECURITY
Short answer
JMS: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.
VerifiedLast verified
01Error text
Error type: JMS:SECURITY02Likely causes
- The exception was thrown because of security-related errors.
03How to fix it
- Check the user name and password in the JMS connection configuration.
- Increase the logging level on the broker and read why it rejected the request.
- 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:SECURITY.
04Official documentation
→Related errors
- 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.
- 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