SAP Knowledge Base Article - Preview

3637722 - How to edit Timeout field in CPI Iflows

Symptom

  • Read timeout errors occur intermittently in Cloud Integration processes.

Error messages include:

  • "com.sap.gateway.core.ip.component.odata.exception.OsciException: Read timed out, cause: java.net.SocketTimeoutException: Read timed out"
  • "com.sap.gateway.core.ip.component.odata.exception.OsciException: Metadata Call returned 200 OK. Exception in reading the response content., cause: java.net.SocketTimeoutException: Read timed out"
  • "com.sap.it.rt.adapter.sfsf.wsclient.SfsfWsClientFaultException: Problem during invoking SuccessFactors Web service. SOAP faultCode SOAP-ENV:Client, faultString Problems creating SAAJ object model, errorCode null, errorMessage: null, cause: java.net.SocketTimeoutException: Read timed out"
  • "com.sap.gateway.core.ip.component.odata.exception.OsciException: HTTP Request failed with error : Read timed out, cause: java.net.SocketTimeoutException: Read timed out"

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.


Read more...

Environment

  • Cloud integrations

Keywords

read timeout, cloud integration, successfactors odata api, sockettimeoutexception, metadata call, saaj object model, http request failed, timeout configuration, iflow timeout, intermittent errors, payload optimization, client session timeout, timeout success factors iflow , KBA , LOD-SF-INT-CPI , Standard SF to 3rd Party CPI (HCI) Content , How To

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.