MuleSoft · JMS Connector
JMS:CONNECTIVITY
Short answer
JMS: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.
VerifiedLast verified
01Error text
Error type: JMS:CONNECTIVITY02Likely causes
- The connection is no longer valid. The connection is disposed of.
- A reconnection policy applies only if one is configured in the app.
03How to fix it
- Check that the broker is running and reachable from the Mule app.
- Configure a reconnection strategy on the JMS configuration.
- 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:CONNECTIVITY.
04Official documentation
→Related errors
- JMS:RETRY_EXHAUSTEDJMS:RETRY_EXHAUSTED means the maximum number of retries for the JMS operation was reached. Find the error each attempt hit, which is logged before this one, and fix that.
- 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.
- MULE:CONNECTIVITYMULE:CONNECTIVITY means there was a problem establishing a connection. It is the parent of connector errors such as DB:CONNECTIVITY and FTP:CONNECTIVITY, so find the connector named in the log and fix or retry its connection.
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