MuleSoft · HTTP Connector
HTTP:RETRY_EXHAUSTED
Short answer
HTTP:RETRY_EXHAUSTED means the maximum number of retries for the HTTP operation was reached. Fix the failure that each attempt hits, which is usually a connectivity problem with the remote host.
VerifiedLast verified
01Error text
Error type: HTTP:RETRY_EXHAUSTED02Likely causes
- The maximum number of retries for the operation is reached.
- Each attempt failed for the same underlying reason, such as a host that cannot be reached.
03How to fix it
- Find the underlying error in the log entries before this one.
- Check the host, port, protocol and TLS settings on the HTTP configuration.
- Handle the failure with an error handler of type
HTTP:RETRY_EXHAUSTED.
04Official documentation
→Related errors
- HTTP:CONNECTIVITYHTTP:CONNECTIVITY means the HTTP Request operation could not establish a connection to the server. Check the host, port, protocol and TLS settings, and add your own retry because the operation does not use the reconnection strategy for retries.
- 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.
- Remotely closedA Remotely closed error means the HTTP connector reused a pooled connection that the remote system had already closed. Set Connection Idle Timeout on the HTTP Request configuration lower than the remote system's idle timeout, for example 10000 to 12000 milliseconds.
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