SAP Knowledge Base Article - Preview

3330076 - "Connection Timed Out"/"Connect Timed Out" error happened while executing an iflow in CPI.

Symptom

  • You're getting a "Connection Timed Out"/"Connect Timed Out" error happened while executing an iflow in CPI.
  • This article covers some frequent types of this kind of error.
    • Type A
      • java.net.SocketTimeoutException: connect timed out (local port 42934 to address x.x.x.x (*** hostname ***), remote port 443 to address y.y.y.y)
      • com.sap.it.rt.adapter.http.api.exception.HttpResponseException: An internal server error occured: connection timed out: *** hostname ***/y.y.y.y:44
    • Type B
      • cause: java.net.SocketTimeoutException: connect timed out (local port 37972 to address x.x.x.x (*** hostname ***), remote port 44300 to address y.y.y.y)
    • Type C
      • cause: io.netty.channel.ConnectTimeoutException: connection timed out: hcp-proxy-xxx/x.x.x.x:8080


Read more...

Environment

  • Cloud Integration

Product

Cloud Integration all versions

Keywords

CPI, CI, Cloud Platform Integration, Cloud Integration, HTTP, Connection timed out, Connect timed out, IP allowlist, allowlist , KBA , LOD-HCI-PI-CON-HTP , HTTP Adapter , LOD-HCI-PI-OPS , Cloud Operations , LOD-HCI-PI-CON-SOAP , SOAP Adapter , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.