MuleSoft · Database Connector
DB:CANNOT_REACH
Short answer
DB: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.
VerifiedLast verified
01Error text
Error type: DB:CANNOT_REACH02Likely causes
- Database Connector cannot establish a connection with the RDBMS.
03How to fix it
- Check the host and port in the Database configuration for the environment the app runs in.
- Confirm the database server is running and reachable from where the app is deployed.
- 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:CANNOT_REACH, or its parentDB:CONNECTIVITY.
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.
- DB:INVALID_CREDENTIALSDB:INVALID_CREDENTIALS means the database rejected the user name or password that Database Connector provided. Correct the credentials in the Database configuration for this environment.
- DB:INVALID_DATABASEDB:INVALID_DATABASE means the connection to the RDBMS was established but the database named in the configuration does not exist. Correct the database name.
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