MuleSoft · HTTP Connector
HTTP:CONNECTIVITY
Short answer
HTTP: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.
VerifiedLast verified
01Error text
Error type: HTTP:CONNECTIVITY02Likely causes
- A problem occurred and a connection could not be established.
- A connection that was open is no longer usable. See the related Remotely closed entry for stale pooled connections.
- The HTTP Request operation does not use the reconnection strategy for retries, so a single failed connection attempt surfaces as this error.
03How to fix it
- Check the host, port and protocol on the HTTP Request configuration against the real address of the service, for the environment the app is running in.
- For HTTPS endpoints, debug the TLS handshake by starting the app with
-Djavax.net.debug=ssl. - Turn on HTTP wire logging to see the exact request and response: in
log4j2.xml, enable the loggerorg.mule.service.http.impl.service.HttpMessageLoggeratDEBUGlevel. - If a retry is safe, wrap the request in an Until Successful scope and set
maxRetriesandmillisBetweenRetries. - Handle the failure with an error handler of type
HTTP:CONNECTIVITY.
04Official documentation
→Related errors
- 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.
- HTTP:TIMEOUTHTTP:TIMEOUT means a request sent by the HTTP Request operation timed out before the response arrived. The wait is set by Response Timeout, which is 10000 milliseconds unless you change it, so raise it or make the remote service answer faster.
- 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.
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