Broken pipe error in Cloud Integration

[#1]

Since the start of June we are seeing failed messages for our integration with error: javax.servlet.ServletException: Error during write of the response: , cause: java.io.IOException: error 32 - Broken pipe.

Though the messages failed in Cloud Integration we can confirmed that the file was delivered to the webservice endpoint successfully. This issue is recurring though there are cases of the same integration flow executions that were successful in Cloud Integration. So the issue is intermittent. Last update of the integration package happens on May 13 so we have no idea what is causing this error. Just to give more context on the integration flow, the integration flow is called via Integration Center as REST API URL and is triggered via an event in ISC (Intelligent Service Center) in SF. We tried replicating it in our internal system but we cannot replicate the same issue reported by our customers.

[bestantetholits]

Hi maik.offerle,

Sorry for the delay in my response. Can you provide further info on how to achieve your suggestion: " higher timeout for synchronous HTTP sessions on the sender system side"?

Thanks!

[maik_bosch]

this is nothing which can be done on CPI side. It is a setting on sender system side. They have to check how long they keep the http session open to CPI. It seems like on their side they only leave it open for 3 minutes. They should change it to 5 minutes or more. See some discussion about advantages and disadvantages here: https://stackoverflow.com/questions/33712208/maximum-reasonable-timeout-for-a-synchronous-http-reque...