MuleSoft · JMS Connector
JMS:RETRY_EXHAUSTED
Short answer
JMS: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.
VerifiedLast verified
01Error text
Error type: JMS:RETRY_EXHAUSTED02Likely causes
- The maximum number of retries for the operation is reached.
03How to fix it
- Find the underlying error in the log entries before this one.
- Check that the broker is running and reachable.
- 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:RETRY_EXHAUSTED.
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.
- MULE:RETRY_EXHAUSTEDMULE:RETRY_EXHAUSTED means every retry of an execution block failed, most often an Until Successful scope whose final retry did not succeed. Fix the error that the processors inside the scope keep raising, or adjust maxRetries and millisBetweenRetries.
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