MuleSoft · Database Connector
DB:RETRY_EXHAUSTED
Short answer
DB:RETRY_EXHAUSTED means all reconnection attempts of a Database Connector operation failed. Fix the connection problem behind the attempts, and review the reconnection strategy.
VerifiedLast verified
01Error text
Error type: DB:RETRY_EXHAUSTED02Likely causes
- All reconnection attempts failed.
- The database stayed unreachable for longer than the reconnection strategy covers.
03How to fix it
- Find the connectivity error logged for the attempts, and fix it.
- Review the reconnection strategy:
countis how many attempts are made andfrequencyis how often, in milliseconds. - Turn on verbose logging: add
AsyncLoggerentries atDEBUGfororg.mule.extension.dbandorg.mule.db.commonsinlog4j2.xml. Turn it off afterward. - Handle the failure with an error handler of type
DB:RETRY_EXHAUSTED.
04Official documentation
→Related errors
- DB:CONNECTIVITYDB:CONNECTIVITY covers several possible connection problems in Database Connector, including a poorly configured connection, no response from the database and a lost connection. Check the connection configuration first, then add a reconnection strategy.
- 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.
- DB:CANNOT_REACHDB:CANNOT_REACH means Database Connector cannot establish a connection with the RDBMS. Check the host and port in the Database configuration and the network path from the app to the database server.
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