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

MuleSoft error
Error type: HTTP:CONNECTIVITY

02Likely 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

  1. 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.
  2. For HTTPS endpoints, debug the TLS handshake by starting the app with -Djavax.net.debug=ssl.
  3. Turn on HTTP wire logging to see the exact request and response: in log4j2.xml, enable the logger org.mule.service.http.impl.service.HttpMessageLogger at DEBUG level.
  4. If a retry is safe, wrap the request in an Until Successful scope and set maxRetries and millisBetweenRetries.
  5. Handle the failure with an error handler of type HTTP:CONNECTIVITY.

04Official documentation

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

The iPaaS Brief

Subscribe to The iPaaS Brief.

The iPaaS newsletter for the people who run integrations. From iPaaS Group.

Free. You finish on theipaasbrief.com and confirm by email.