3360837 - Problem during invoking SuccessFactors Web service: Premature EOF

You have an integration on CPI that calls SuccessFactors API, but fails with error 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.io.IOException: Premature EOF

• SuccessFactors HXM Suite
• Cloud Integration Platform

• ISSUE 1: The iFlow is not correclty using Session Reuse;
• ISSUE 2: When a call is made to Successfactors system in the first iteration it issues a Session id, this session if left idle, is available only for 10 minutes. The artifact first iteration is taking more than 10 minutes, the second iteration fails because the session is no longer available.

ISSUE 1: When setting up an iFlow, you are able to use 2 methods of "Session Reuse":

1. On Exchange: Each exchange corresponds to a single session.
2. On Integration Flow: Only one session will be used across the whole integration flow.

On scenarios where you expect the integration to take a long time to complete, and hence needs CPI to update it's Session as peer SuccessFactors JSESSIONID, please use On Exchange (you might find more information on Specify the Runtime Configuration).

To performe this change:

1. Open the iFlow
2. Click on any empty space
3. Expand the configuration of the iFlow
4. Go to Runtime Configuration
5. On HTTP Session Reuse, select On Exchange

======================================================

ISSUE 2:

One way to avoid the problem is to reduce the batch size and try. Please try with smaller batch size and gradually increase it to the number from where the iFlow is able to process the data without failing. Our suggestion would be to try first with 200, then 100, then 50.

INVALID_SESSION, CPI, EOF , KBA , LOD-SF-INT-API , API & Adhoc API Framework , Problem