SAP Knowledge Base Article - Preview

2499167 - Handling Timeout and Connection Reset Errors in Cloud Integration Runtime

Symptom

When you are trying to run a integration flow, and it encounters a Request Timeout or Connection Reset error as shown below:

  1. com.sap.gateway.core.ip.component.odata.exception.OsciException - java.net.SocketTimeoutException: Read timed out (local port XXXX to address XX.XXX.XX.XX (XXXXXXXXXX), remote port XXXX to address XX.XX.XXX.XX (XXXXXXXXXX))], cause: java.net.SocketTimeoutException: Read timed out (local port XXXX to address XX.XX.XX.XX (XXXXXXXX), remote port XXXX to address XX.XX.XXX.XX XXXXXXXXXXX))
  2. HTTP Request failed with error: executeUtil : failed with error. Message = Message processing timed out after 1 minute(s) as configured in OData v2 adapter read. Read time out
  3. com.sap.gateway.core.ip.component.odata.exception.OsciException: HTTP Request failed with error : Connection reset, cause: java.net.SocketException: Connection reset


Read more...

Environment

SAP Cloud Integration

Product

SAP Cloud Platform Integration for process services 1.0 ; SAP Integration Suite all versions

Keywords

SAP Cloud Integration, SAP HCI, SAP CPI, SCPI, SFSF, tenant, IFlow, Integration Flow, deployment, model configurator, properties, tracing, payload, CPI integration flow, timeout, time out, Cloud Integration, org.apache.cxf.interceptor.Fault, Could not send Message, java.net.SocketTimeoutException, Read timed out, Successfactors, OData v2, HTTP , KBA , connection time out , icm_http_connection_broken , LOD-HCI-PI-CON-OD , OData Adapters , Problem

About this page

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

Search for additional results

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